Provide Github Labels for Filtering
We'd really like to access github labels in a ignore/only filter statement (similar to git tags). This would allow us to:
Mark PRs that shouldn't be built at all (effectively preventing the PR from being merged)
Mark PRs to build and unit test, but skip the integration tests
Mark PRs for deployment to a specific staging environment
IMO, that would improve circleci's capabilities in multi stage deployment scenarios.
And, this has already been proposed here: https://discuss.circleci.com/t/tag-label-filter/11158
Is this feature available ? Seems a very useful one and could definitely benefit.
Is there any movement on this? It seems to be a useful feature that has been requested since 2018
Merged in a post:
Allow OSS project teams to mark approved PR Builds
For large scale OSS teams who are paying for performance plans, they would like the ability to "approve" Pull Requests that should be allowed to consume their credits.This has been solved in other tools by looking for a specific label on the PR that a project maintainer has added, indicating it is not malicious bit mining, etc.
This is a duplicate of/duplicated by https://ideas.circleci.com/cloud-feature-requests/p/provide-github-labels-for-filtering
Peter Boling: Thanks Peter! I'll merge these. We did some clean-up & merging of ideas when we transitioned over last year, but there are still some one-offs out there. Appreciate the help.
Liya Ai: You are welcome! We will be stopping our paid plan soon if this is not implemented. We have a devops team, and are building out JX, and are almost to the point of putting in effort to replace CIrcleCI. Hoping you can get to this so we can put the effort somewhere else!
Would go very far in helping us streamline some tedious workflows!
This needs to happen. I need this feature for dozens of repos to work acceptably with Depfu, Greenkeeper, Renovate, and other similar services. How is this not already a thing?!
Merged in a post:
Executable jobs depening on (Github) Labels
This could be useful to activate or deactivate special job sets with given labels.
- You could label your PR as dependency upgrade (thus all pipelines should run)
- You also label another PR with bugfix and only Unit and regression tests should run against your product
Pros: saving computing/people's time, activating specialized test sets for special labels, more specific testing abilities
Cons: Over-Engineered CI systems, missing tests if labels are missing (or too much depending on the setup)
This would be a great feature for CircleCI to have! Thanks for the link with a script!
Came here for this. I recently made a python script that creates and pushes a git tag that starts with "feature-", which CI deploy scripts use to create and update feature branch deployments. But wouldn't it be so much easier if Circle CI detected when a PR is labeled with something like