Skip to content

feat(release): a Skip QA button in the QA step - #17

Merged
rjd15372 merged 1 commit into
mainfrom
feat/skip-qa
Nov 13, 2026
Merged

rjd15372 merged 1 commit into
mainfrom
feat/skip-qa

Conversation

@rjd15372

Copy link
Copy Markdown
Collaborator

What

The QA step of the release wizard gets a Skip QA button, for when QA already ran on an earlier iteration of the release PR.

  • Shown while QA has not finished: before approval, while it runs, or when it could not start.
  • A red dialog with a warning must be confirmed.
  • After the skip, Release becomes available; its own confirmation is red and says QA was skipped.
  • The skip covers the current head of the PR only. "Update to latest main & restart" asks for QA again.
  • A comment on the release PR says QA was skipped for that commit. It does not name the user: emails stay in the dashboard.

How

  • New action skip-qa. The skip is an audit row (skip_qa) whose detail is the PR head.
  • Release is accepted when QA finished or the skip is recorded for the exact head. Failed lanes still need their confirmation.
  • If the comment cannot be posted, nothing is skipped.

Tests

Backend and frontend tests cover the action, its refusals, the head scope, and the page. Not tried against real GitHub.

After a warning and a confirmation, a user can make Release available
without QA for the current head of the release PR. The skip is kept in
the audit log with the head it is for, so a re-cut asks for QA again,
and a comment on the PR says QA was skipped. The comment does not name
the user.

Signed-off-by: Ricardo Dias <ricardo.dias@percona.com>
@rjd15372
rjd15372 merged commit b6e36ac into main Nov 13, 2026
5 checks passed
@rjd15372
rjd15372 deleted the feat/skip-qa branch November 13, 2026 10:38
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant