Info |
---|
These are playbooks for on-call tasks. Feel free to add more! |
...
Most requests will come from folks who are following the instructions on page: https://openedx.atlassian.net/wiki/spaces/COMM/pages/3241640370/tCRILAxim+Collaborative+Engineering+Team#tCRILTeam#Axim-Request-Process . Familiarize yourself with those instructions so that you understand what is expected of the requester. Update the that page if it seems like any part of it is incorrect or causing confusion.
...
Set the Account Name to the relevant Institution(2U/edx, OpenCraft, etc.)
The contributor's first and last name
The contributor's GitHub username (case sensitive - it should match what you see on their profile at
https://github.com/<username>
)Ideally, their email address
Locate the field Contributor Covered Under Entity and select it
Locate the Role field and add the
Entity Contributor
role to the user.
...
Finally, if a repo is meant to only hold issues (that is: only a README, catalog-info, gitignore, and GH workflows; NO code, docs, or assets), then click the gear next to the repo’s description and apply the issues-only
topic. Then, to ensure that all Coding CCs can flexibly work with issues on the repo, grant:
core-contributor-program-committers
committers
(GitHub group) - write access
🏗 Transferring repositories into openedx
...
Go to the Open edX org Renovate GitHub app installation page and add the requested repo under “Only select repositories” in “Repository access”
🔏 Adding Secrets to the Openedx Github Org
For each org secret, we want to document how to rotate the secret as well so as a part of the process of adding it, you should also update /wiki/spaces/~feanil/pages/3251372059 with an entry for the new secret you’re adding. If it got accidentally exposed, what steps would we need to take to re-create it?
Go to /wiki/spaces/~feanil/pages/3251372059 and add an entry for how to rotate the new secret.
Go to https://github.com/organizations/openedx/settings/secrets/actions
Add the new secret.