GSoC 2026 - Desired workflow for GitHub Workflow Hooks proposal

Open Source Development Google Summer of Code
1

I'm preparing a proposal for the GitHub workflow hooks project and wanted to confirm my understanding of the current and desired workflow.

PR Lifecycle

  • PR is opened → automatically label needs review
  • affects: master and affects: ucr should be automatically set from the PR target branch.
  • Review begins → remove needs review and add in review
  • Reviewer requests changes → add needs reply to review
  • PR is approved → remove needs reply to review, remove in review, and add pull request: ready to push to Gerrit

Issue Lifecycle:

  • Issue opened → label status: new
  • PR merges into master closes linked issues and removes status: new
  • PR merges into ucr removes status:new and adds issue: pending component release
  • New release tag → closes all issues with issue: pending component release and removes the label.

Other Questions

  • Is the label Is Still Draft based off the draft status of the PR or some other criteria? I see draft PRs without the label and vice versa, ready-for-review PRs with the label.
  • Is Gerrit used to merge every PR or only select ones?
  • Would it be helpful to automatically prevent conflicting labels, such as having status: new and status: in progress simultaneously?