create a permanent 'documentation' branch

[umlaeute]

similar to the devel branch, we should have a documentation branch in the main Pd repository pure-data/pure-data.

• people can create PRs against this branch
• @porres should be able to push to that branch

thoughts

every now and again somebody comes up with a small documentation fix which they submit as a PR against the master branch.
having to tell them to create a new PR in a different repository is rather unfriendly (and while we can re-target a PR to a different branch in the same repository, we cannot re-target it to a different repository)

to be honest, I would like to restrict @porres to only be able to push to this documentation branch (so we don't get accidental pushes to e.g. master) (sorry bro, but I'm still not 100% convinced of your git foo 😜 🥷 )

while porres' docs branch has traditionally been called Documentation, I would suggest to use documentation (all lower-case) for that branch - virtually all branches in the main repository use a lowercase spelling (with exceptions for abbreviations like API)

[ben-wes]

sounds good - although for me all options are fine (besides my definite lack of actual git foo). what was a little confusing about my previous PR was that i tried to follow the instructions on https://github.com/pure-data/pddp, which state that Documentation changes regarding contents of https://github.com/pure-data/pure-data (manual/help files) should be made via a PR to that repository.

i just mentioned this in the updated PR as well: porres/pure-data#34 (comment)

[porres]

sounds great

[umlaeute]

• created documentation branch
• migrated the old "Documentation updates" PR to Documentation fixes pure-data#2147
• created a @pure-data/docs team for documentation writers
• updated branch protection rules, so the @pure-data/docs team can push
• invited @porres to the docs team
• @porres accepted membership to the team