News for hackers. Stuff that matters.

A comment on Ask HN: How does your team handle knowledge documentation?. Parent comment

Re:Ask HN: How does your team handle knowledge documentation? by clintonb on Monday November 06, 2017 @02:06PM (#15637985)
Why not relax the PR process for the docs directory? If your process is in the way of progress, change the process!
[ Parent | on HN ]
Re:Ask HN: How does your team handle knowledge documentation? by dalemyers on Monday November 06, 2017 @02:32PM (#15638291)
We can't unfortunately. With Github it's all or nothing. We need to enforce code reviews for all merges for certain branches anyway for legal reasons.
[ Parent | on HN ]
Re:Ask HN: How does your team handle knowledge documentation? by OJFord on Monday November 06, 2017 @06:29PM (#15639908)
So why not have a docs branch open for direct commits, and then merge it into 'certain branches' at meaningful points - release, or whatever?
[ Parent | on HN ]