-
-
Notifications
You must be signed in to change notification settings - Fork 40
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
author-can-merge: false does not seem to work #123
Comments
Hi @jrfnl, what version are you using? |
Nevermind, I just pushed a fix. I've added an extra test with the final condition you wanted to set. |
Should be fixed in https://github.com/srvaroa/labeler/releases/tag/v1.8.1 Thanks for reporting. Let me know if this works as expected |
Thank you for the quick response @srvaroa ! I am using |
I will update v1 to point at v1.8.1 first thing tomorrow! |
v1 is updated |
All PRs are being labeled "external-contribution". This is probably because of srvaroa/labeler#123, which has been resolved in the latest v1 release. I updated the version of the action to the latest v1 version.
@srvaroa I've been checking new PRs for a few days now and something still doesn't seem right. The "triage" label now gets added to all PRs, even those of people who can merge in the repo. |
Hi @jrfnl i will take a look asap. Is this in a public repo where I can take a look at the logs? |
@srvaroa Appreciated and yes, the repo is public. Sorry, I didn't add links before as, while the repo is public, the news that the repo existed was not, but an announcement was made last week ;-) Workflow file: https://github.com/PHPCSStandards/PHP_CodeSniffer/blob/master/.github/workflows/label-new-prs.yml Here is one where the "triage" label now correctly got added for a contributor who doesn't have commit: https://github.com/PHPCSStandards/PHP_CodeSniffer/actions/runs/7144614939/job/19458612350 |
author-can-merge was not considering all the roles that allow for committing into the base branch Fixes: #123 Signed-off-by: Galo Navarro <anglorvaroa@gmail.com>
author-can-merge was not considering all the roles that allow for committing into the base branch Fixes: #123 Signed-off-by: Galo Navarro <anglorvaroa@gmail.com>
@jrfnl it looks like the implementation of that condition was not considering all the roles that allow for committing to the base branch, only OWNER. This is released as v1.8.2, the v1 floating reference is also updated. Let me know if this makes things work as expected. |
Interesting as I would have expected that repo to identify me as an owner too. Could this be because this repo was originally a fork and was "decoupled" ?
Will do! Thanks @srvaroa for working on this! |
I noticed in the logs you linked above that the action resolved the author as non-owner, so I suspected this was the problem. The fix is needed anyway, but do let me know if it doesn't evaluate as expected for your PRs and I'll look further into it. Thanks for the bug reports! |
It may be a few days/week before I have enough info to evaluate fully. There are basically three kind of PRs I'd like to see come in to be able to say for sure:
Will let you know how I get on. |
Hiya,
As one of the criteria in a
labeler.yml
file, I have the following:I'd expect
The
Status: triage
label to be added to all non-draft PRs where the author doesn't have commit rights in the repo.What actually happened
The
Status: triage
label does not get added to PRs from outside contributors (who don't have commit rights to the repo).Other info
I haven't tested yet if it works when I set it as follows, but if it does, I'd still find that counter-intuitive, as I'd expect
author-can-merge: false
to be respected.The text was updated successfully, but these errors were encountered: