Repository navigation
Add a require label workflow - #90
Open
paulinevos wants to merge 1 commit into
Open
paulinevos wants to merge 1 commit into
paulinevos wants to merge 1 commit into
Conversation
paulinevos
commented
Nov 5, 2026
paulinevos
commented
Nov 5, 2026
| jobs: | ||
| check: | ||
| name: "Pull request has a label" | ||
| uses: "doctrine/.github/.github/workflows/require-label.yml@use_a_valid_ref_here" |
Member
Author
There was a problem hiding this comment.
Maybe pin to this commit SHA instead of "use_a_valid_ref_here" lol
paulinevos
force-pushed
the
require-label-workflow
branch
from
November 5, 2026 13:30
707f9dd to
4213116
Compare
greg0ire
reviewed
Nov 5, 2026
paulinevos
force-pushed
the
require-label-workflow
branch
from
November 5, 2026 13:34
4213116 to
ff052b0
Compare
paulinevos
marked this pull request as ready for review
November 5, 2026 13:36
There was a problem hiding this comment.
Warning
Copilot couldn't run its full agentic review because it didn't start before the timeout. Make sure your repository has a runner available, or add a copilot-code-review.yml file specifying one with the runs-on attribute. See the docs for more details.
Copilot review overview
5 open issues
opened,labeled, andunlabeled, but the workflow… · Newworkflow_call,github.event_nameisworkflow_call, not… · New
What changed in this PR
Adds a GitHub Actions workflow intended to fail when a pull request has no labels, via a reusable workflow and a local caller workflow.
Changes:
- Added a workflow template YAML + properties card for a “Require label” workflow.
- Added a repository workflow intended to run on PR label and review events and call a reusable workflow.
- Implemented label-check logic using
gh apiand failing with an::error::annotation when label count is zero.
| File | Description |
|---|---|
| workflow-templates/require-label.yml | Adds the label-check job logic intended for reuse/template distribution. |
| workflow-templates/require-label.properties.json | Adds the workflow template metadata card for GitHub’s workflow template picker. |
| .github/workflows/require-label.yml | Adds a workflow that triggers on PR events and calls a reusable workflow by uses:. |
Review effort: Lite
Copilot stopped reviewing on behalf of
paulinevos due to an error
November 5, 2026 13:41
paulinevos
force-pushed
the
require-label-workflow
branch
from
November 5, 2026 15:06
ff052b0 to
60d9c31
Compare
greg0ire
reviewed
Nov 5, 2026
| name: "Pul 8000 l request has a label" | ||
| runs-on: "ubuntu-latest" | ||
| # Every review fires pull_request_review; only approvals re-run the check. | ||
| if: "github.event_name != 'pull_request_review' || github.event.review.state == 'approved'" |
Member
There was a problem hiding this comment.
I don't think I understand the comment and the condition. Didn't we say that it would be useful to have it as soon as a review was posted (even if there wasn't an approval)?
There was a problem hiding this comment.
Warning
Copilot couldn't run its full agentic review because it didn't start before the timeout. Make sure your repository has a runner available, or add a copilot-code-review.yml file specifying one with the runs-on attribute. See the docs for more details.
Copilot review overview
3 open issues
5 resolved since last review
workflow_call,github.event_nameisworkflow_call, not…opened,labeled, andunlabeled, but the workflow…
Review effort: Lite
| env: | ||
| GH_TOKEN: ${{ github.token }} | ||
| run: | | ||
| label_count="$(gh api "repos/${{ github.repository }}/issues/${{ github.event.pull_request.number }}" --jq '.labels | length')" |
| name: "Require label" | ||
|
|
||
| on: | ||
| workflow_call: |
Comment on lines
+20
to
+25
| run: | | ||
| label_count="$(gh api "repos/${{ github.repository }}/issues/${{ github.event.pull_request.number }}" --jq '.labels | length')" | ||
| if [ "${label_count}" -eq 0 ]; then | ||
| echo "::error::No label is applied to this pull request. Add a label so it can be triaged." | ||
| exit 1 | ||
| fi |
Copilot stopped reviewing on behalf of
paulinevos due to an error
November 5, 2026 15:34
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Adds a reusable workflow that fails when no label is applied to a pull request.
workflow-templates/require-label.ymlqueries the pull request via the API and fails with an::error::annotation when it carries no labels. It needs onlypull-requests: readand never checks out the pull request head.workflow-templates/require-label.properties.jsonis the template card, matching the existing templates.This repository is the template source: the workflow is meant to run in the repositories consuming it, so no caller lives here. A consumer calls it with triggers
pull_request(labeled,unlabeled) andpull_request_review(submitted); inside the reusable workflow a job-level condition skips every review that is not an approval. It deliberately does not run when a pull request opens, so an unlabelled pull request is only flagged once someone approves it. Adding a label re-runs the check and flips an earlier failure back to green.The check blocks merges: consumers should mark it as a required status check so a pull request without a label cannot be merged. It does not block other actions: it is standalone, so no other job or workflow may depend on it.