Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Please add a way to disable the 'can one of the admins verify this patch' comment
See original GitHub issueIf you have rather strict rules on whether you are allowed to trigger tests or not, you can’t enable the Build every pull request automatically without asking (Dangerous!). option which would disable the warning.
I found the option to change the default message, which is nice but simply not enough. We have multiple jobs with the jenkins pr builder that point to one repo and can be triggered by different trigger phrases. By not having the possiblity to disable these comments every new contributor gets flooded with these messages.
So my request would be to have a job-wide(not system-wide) switch to toggle these warnings.
Issue Analytics
- State:
- Created 6 years ago
- Reactions:13
- Comments:11 (1 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
Can one of the admins verify this patch? 🙄
We’ve been running into this issue with our Jenkins setup, such as on this PR https://github.com/opensearch-project/OpenSearch/pull/1943