Nixpkgs committers

This repository publicly tracks the current members and changes of the Nixpkgs Committers team, whose members have write access to Nixpkgs.

The Nixpkgs core team maintain the member list in this repository according to the documented procedures.

Nominations

To nominate yourself or somebody else:

1. Check open nominations to make sure the user hasn't been nominated already.
2. Click this link to create a new file in the members directory.
3. Leave the file contents empty and replace <GITHUB_HANDLE> with the handle (without @) of the user you'd like to nominate .
4. Click on "Commit changes..." and follow the steps to create a PR.
5. State your motivation for the nomination in the PR description.

Such nominations are also automatically announced in this issue, which you can subscribe to for updates.

Semi-automatic synchronisation

Every day, a GitHub Action workflow runs to synchronise the members of the GitHub team with the member list in this repository. If they don't match, an automated PR is created, which should be merged by the Nixpkgs commit delegators to reconcile the mismatch.

Semi-automatic retirement

Every day, a GitHub Action workflow runs to check if any Nixpkgs committers have not used their commit access within the last year, in which case an automated PR is created to remove them from the member list. This is according to RFC 55 and the SC-approved amendment.

The PR will ping the user and inform them that it will by default be merged and implemented in one month. If the PR is still open one month later, an automated comment will be posted with the next steps for the Nixpkgs commit delegators.

If the PR is closed, retirement is delayed by another year.

Automation setup

Automation depends on a GitHub App with the following permissions:

• Organisation: Members read only (to be able to read the team members)
• Repository: Pull requests read write, Contents read write (to be able to create PRs in this repository)

The GitHub App should only be installed on this repository. To give the workflows access to the GitHub App:

• Configure the App ID as the repository variable APP_ID
• Configure the private key as the repository secret PRIVATE_KEY