Commit dc0c1956 authored by Sid Sijbrandij's avatar Sid Sijbrandij

Merge branch 'add-where-content-lands-in-hb' into 'master'

Add to provide where you expect content to land in handbook when collaborating

See merge request !28408
parents f6b4a442 8e8a5ffe
Pipeline #78067596 passed with stages
in 29 minutes and 39 seconds
......@@ -20,6 +20,8 @@ Only do this for things that are unlikely to break the tests, so modifying markd
In this case you need to be OK with reverting them if they are contentious.
As soon as we have [git push option to merge when pipeline succeeds]( nobody can push to master anymore and this section should be removed.
Sometimes you want to have real time editing of a proposal during a meeting and you need to use a Google Doc for that. When doing so the first item should be the URL of the handbook page this content will be moved to when the meeting is over.
## Why handbook first
Documenting in the handbook before taking an action may require more time initially because you have to think about where to make the change, integrate it with the existing content, and then possibly add to or refactor the handbook to have a proper foundation. But, it saves time in the long run, and this communication is essential to our ability to continue scaling and adapting our organization.
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment