Label changes in GitHub are ignored after a PR has been opened
See original GitHub issueThe recently added label whitelist/blacklist feature has an annoying bug: if you whitelist a label but forget to add that label when you first open the PR, adding the label later and commenting “test this please” still doesn’t trigger the PR builder. The log contains entries like this
Mar 20, 2017 5:46:02 PM org.jenkinsci.plugins.ghprb.GhprbPullRequest checkWhiteListLabels
INFO: Can't find any of whitelist label.
even though the whitelist label is now set on the PR in question. The only fix appears to be to close and reopen the PR with the label in place to begin with.
This was also noted at https://github.com/jenkinsci/ghprb-plugin/pull/449#issuecomment-273789412
Issue Analytics
- State:
- Created 7 years ago
- Reactions:13
- Comments:10 (2 by maintainers)
Top Results From Across the Web
Configuration Options - Renovate Docs
Important: Renovate won't automerge on GitHub if a PR has a negative review ... see if an update PR was created previously, and...
Read more >Push policy - Spacelift Documentation
Pull request events are supported for some VCS providers and are generally received when you open, synchronize (push a new commit), label, or...
Read more >Build GitHub repositories - Azure Pipelines - Microsoft Learn
Pull request (PR) triggers cause a pipeline to run whenever a pull request is opened with one of the specified target branches, or...
Read more >Configuration Reference - Kodiak
Show a status message when automerge label is required but missing on a PR. When disabled, no status message is shown until the...
Read more >Running GitHub Actions only on certain pull requests
A common need is to trigger an action for a pull request matching ... when a pull request's label changes, and filter based...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Hi can we merge the fix for this? https://github.com/jenkinsci/ghprb-plugin/pull/804
Would be extremely useful if we can get this out.
Hi @bjoernhaeuser , is there any movement on this issue? This PR has been suggested almost two years ago as a solution: https://github.com/jenkinsci/ghprb-plugin/pull/639 Any reason why it’s still not merged? It seems like a fundamental drawback in the plugin.