qa-label

Labels a GitHub pull request as ready for QA to trigger automated browser tests.

12.1k|1.5k|Updated Jul 12, 2023

Search Tags:#QA #browser tests #Automation #gh CLI #gitHub #label #Pull request

Ready to run

npx skills add https://github.com/elie222/inbox-zero --skill qa-label

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: qa-label
Source: https://github.com/elie222/inbox-zero/tree/main/.claude/skills/qa-label
Command: npx skills add https://github.com/elie222/inbox-zero --skill qa-label

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Manually notifying QA or triggering test runs for a pull request adds friction to the review cycle. This Skill marks a PR with the "ready-for-qa" label so the QA server automatically picks it up and runs browser tests against the branch.

Core Features & Use Cases

One-command QA trigger: Adds the "ready-for-qa" label to any PR using the GitHub CLI.
Automatic test execution: The QA server detects the label within about 60 seconds and runs browser tests against the PR branch.
Continuous retesting: New pushes to the PR automatically retrigger tests while the label remains.
Use Case: After finishing a feature branch and opening a PR, label it ready for QA so browser tests run without any manual handoff to the QA team.

Quick Start

Mark pull request number 123 as ready for QA so the automated browser tests run against it.

Frequently Asked Questions about qa-label

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I trigger automated QA tests on a GitHub pull request?▼

Add the ready-for-qa label to the PR by running gh pr edit <PR_NUMBER> --add-label "ready-for-qa". The QA server detects the label within about 60 seconds and runs browser tests against the PR branch.

How to add a label to a pull request with GitHub CLI?▼

Use the command gh pr edit followed by the PR number and the --add-label flag with the label name. For example, gh pr edit 42 --add-label "ready-for-qa" applies that label to PR 42.

Do QA tests rerun when I push new commits to the PR?▼

Yes, new pushes to the PR branch automatically retrigger the QA browser tests as long as the ready-for-qa label remains on the pull request. No additional commands are needed.

How long does it take for the QA server to pick up a labeled PR?▼

The automated QA process on the QA server picks up a newly labeled PR within approximately 60 seconds. It then runs browser tests against the PR branch.

What happens if I remove the ready-for-qa label from a PR?▼

Removing the label stops the automatic retriggering behavior, so new pushes to the branch will no longer cause the QA server to run browser tests against that pull request.