ci(labeler): call the QAtlasHub reusable workflow instead of gh pr edit - #30
Merged
Conversation
|
Comments on pull requests will not trigger Registrator, as it is disabled. Please try commenting on a commit or issue. |
Codecov Report✅ All modified and coverable lines are covered by tests. 📢 Thoughts on this report? Let us know! |
Contributor
|
📚 Docs preview: https://QAtlasHub.github.io/ParallelManager.jl/previews/PR30/ (updates on each push to this PR) |
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.
Warning
Merging this cuts a release. This repo is public, so AutoRegister answers the
Project.tomlbump on main with a@JuliaRegistrator registercomment → General registry.The bump is not optional (VersionCheck runs on every PR by design), so v0.4.1 → v0.4.2 is
the price of a CI-only change here. Hold the merge if you do not want v0.4.2 published.
Description
gh pr edit --add-labelreads the pull request over GraphQL, and GitHub now answers that querywith the Projects-classic sunset notice (
repository.pullRequest.projectCards);ghreports itas an error and exits 1. The hand-rolled
PRLabeler.ymltherefore fails on a deprecation messagethat has nothing to do with labelling — measured on lab-sotashimozono/FunctionMeasures.jl, green
on 07-27 and red on 07-28, with no change to the workflow.
40 repos across lab-sotashimozono / QAtlasHub / sotashimozono carried that copy. This replaces
it with the thin caller of the reusable workflow that already serves 4 repos, so the
implementation lives once in
QAtlasHub/.github(labeler.yml@v1,fixed in QAtlasHub/.github#18) and the next breakage is one commit there instead of one PR per repo.
Behaviour is preserved: same six labels, same colours (created on demand), same
Type-of-Change checkbox parsing, and
breakingis still removed when its box is unticked.A public repo takes the workflow's default runner (
ubuntu-latest), so the caller needs no inputs.Type of Change
chore)Proposed Changes
.github/workflows/PRLabeler.yml→ thin caller ofQAtlasHub/.github/.github/workflows/labeler.yml@v1Project.tomlv0.4.1 → v0.4.2 (VersionCheck runs on every PR, deliberately, so aworkflow-only change still needs the bump)
Usage or Results
This PR labels itself: the
chorebox above is what the reusable workflow reads, so a greenPR Labeler check plus a
chorelabel on this PR is the end-to-end proof that the replacementworks in this repo.