ansible-collections/community.general
1
0
Fork 0
mirror of https://github.com/ansible-collections/community.general.git synced 2025-07-01 12:40:22 -07:00
Code Issues Projects Releases Packages Wiki Activity Actions 8

Documentation on how to make a release. (#31426)

Browse source 
* Release Engineering Docs with pointer to the Docs on how to actually make the release.
This commit is contained in:
Toshio Kuratomi 2017-12-21 08:14:49 -08:00 • committed by GitHub
parent ebd096a732
commit 94d952f94b
No known key found for this signature in database
GPG key ID: 4AEE18F83AFDEB23
4 changed files with 116 additions and 0 deletions
Download patch file Download diff file Expand all files Collapse all files

29
docs/docsite/rst/community/github_admins.rst Normal file
View file

@ -0,0 +1,29 @@
GitHub Admins
=============
.. contents:: Topics
GitHub Admins have more permissions on GitHub than normal contributors. There are
a few responsibilities that come with that increased power.
Add and Remove Committers
-------------------------
The Ansible Team will periodically review who is actively contributing to Ansible to grant or revoke
contributors' ability to commit on their own. GitHub Admins are the people who have the power to
actually manage the GitHub permissions.
Change Branch Permissions for Release
-------------------------------------
When we make releases we make people go through a :doc:`release_manager` to push commits to that
branch. The GitHub admins are responsible for setting the branch so only the Release Manager can
commit to the branch when the release process reaches that stage and later opening the branch once
the release has been made. The Release manager will let the GitHub Admin know when this needs to be
done.
.. seealso:: The `GitHub Admin Process Docs
<https://github.com/ansible/ansible/blob/devel/hacking/release-branches.rst>`_ for instructions
on how to change branch permissions.