Managing Git access and access to opt into security advisory coverage

Last updated on
14 January 2021

Git access has licensing and legal implications, and is managed via Git access agreement available to people when they edit their accounts.

Granting Git access

Each individual person can to edit their own account and accept Git access agreement to gain the role. Administrators cannot grant Git access agreement for the user.

Git administrators give people the permission to opt into security advisory coverage.

Giving people access to opt into security advisory coverage

Check the quality of reviews on Reviewed and Tested By the Community (RTBC) applications and give the user applying vetted status.

Go to the user’s account, click “Git access”, and check “Is a vetted user” at the end of that form and save, with no other changes. You can directly approve applicants, there is no need for a project application to be reviewed by multiple Git admins.

Set the application issue status to Fixed and post the promotion template to welcome the git vetted user.

Revoking Git access

If the Git access agreement is not followed, and the person has been warned and advised of a better way to do things, Git access can be revoked. This change can be done on the user’s Git Access agreement page itself:

How to get Git administrator access

Having been granted the ability to promote your own projects, of course, and shown your ability in doing application reviews for a long, sustained time, apply at Drupal.org site moderators issue queue.

Help improve this page

Page status: No known problems

You can: