-
Notifications
You must be signed in to change notification settings - Fork 503
Pull Request Czar Role
Somebody on the team will be designated the "PR Czar" for the month. Their job is to keep track of the ongoing pull requests for the project. Everyone will need to serve as the Czar at least once a year. If you are the Czar, you will receive an automatic email each morning of the current open PRs.
The PR Czar schedule is available in a Google doc. See slack for more info.
Responsibilities:
-
Make sure that each PR is tagged with the proper category and status labels. If a PR is not ready for review, then it should be tagged as
in-progress. -
Assign reviewers to any PR that is tagged as
ready-for-review. If you unsure about who to assign for the review, ask Andy or Pervaze. -
If a PR is marked as
ready-to-merge, make sure that it passes all of the tests on both Jenkins and Travis. You can then merge it yourself, or ask somebody else to merge it for you.
Carnegie Mellon Database Group Website