Quick Facts
2 week sprint-aligned rotation within standard business hours.
@openedx/tcril-oncallis the GitHub group.Ask for help if you need it!
Upcoming Schedule
Schedule. Please adjust as appropriate:
...
📒 What are the responsibilities?
Respond to GitHub Requests within one business day. See inline instructions for “Common Requests”.
Requests should automatically ping the
@openedx/tcril-oncallGitHub group.Assign yourself to the issue.
If you can’t resolve the request within a day, that is fine. Just give an “Ack” and a general timeline estimate.
Review and merge CLA PRs, delete related branches. Currently a PR is created daily, many of which are empty – we’ll work on improving the Zap to account for this.
| Expand | ||
|---|---|---|
| ||
If you get a pull that has a new organization’s name in it, you’ll get a failure on the build. You’ll need to add the new org’s info (found in Salesforce; attached to the account record in the “related” tab under contracts) to orgs.yaml. Reference PR: https://github.com/edx/repo-tools-data/pull/171 |
...
Ensure each GitHub Request is either closed within the sprint or explicitly reviewed & handed off to the next on-call engineer at the beginning of the following sprint.
If you are swamped during the sprint, delegate to other team members!
...
Respond to other pings to the @openedx/tcril-oncall group if they happen.
...
See On-call Playbooks - add new things there!
🌀 How does the rotation work?
...