-
-
Notifications
You must be signed in to change notification settings - Fork 16
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
bug: "Invalid value 'ready' labels.Status: Ready.labeled.pr.action" #568
Comments
Also, to add to this: I previously used |
It just has not been released. |
Sorry for such a late reply: What is the solution now? |
Okay. I've updated the action to use The latest workflow run where this happens (Debug was enabled): https://github.com/Readme-Workflows/recent-activity/runs/8293723349?check_suite_focus=true |
Checklist
RUNNER_DEBUG: 1
for debugging.Describe the bug
Currently, use this action to mark a PR as Draft or ready depending on the labels added/removed.
When I was using it today, I noticed that while the action does comment on the PR, did it not change the PR's state to Ready.
Checking the latest examples and docs here, I saw that
draft: true
changed toaction: ready
, so I tried this now, but the action now failed with the messageInvalid value "ready" labels.Status: Ready.labeled.pr.action
despite this being 1:1 the same in thelabel-commenter-config.yml
file:actions-label-commenter/.github/label-commenter-config.yml
Lines 23 to 25 in feeed63
Yes, I am using a dedicated User account here and the account has sufficient permissions to change a PR's state. This action worked before but now doesn't.
Relevant links
Relevant log output
Additional context.
As mentioned above did this action work perfectly fine before and PRs were marked as Ready or Draft.
The example file on this repository mentions
action: draft
andaction: ready
for PRs so someone would guess it's actually what you need to mark a PR properly, but the fact that it fails means that there must be an issue.The text was updated successfully, but these errors were encountered: