-
Notifications
You must be signed in to change notification settings - Fork 432
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
Support for output #59
Comments
FYI: I made PR for this: #60 We've made the change locally and are using it happily. Would love to get this PR in and switch back to using the official action. Thanks! |
Another use-case for this is to run different unit-tests in the CI based on the updated labels. E.g. run back-end v.s. front-end tests or build different docker images. |
Any way to get that out? I see a couple of forks that added that behaviour, is there anything preventing that to go through? @MaksimZhukov ? Thank you :) |
Hi. I am also wanting to see outputs in the official labeler action rather than using a fork. Thank you. |
Hello everyone! |
I'm using this action as one step in a multi step (job actually) workflow. I would like to have this action label PRs based on the files changed, but subsequently assign reviewers based on those labels. Here is a sample of my workflow:
The problem here is that the
github.event.pull_request
object is created before the entire workflow runs and is not updated when this specific action runs. Sogithub.event.pull_request.labels
is not affected by this action.One solution would be for this action to produce an output of the labels changed (or better yet, the labels of the PR) so that it can be used in subsequent jobs that run sequentially.
Thanks!
The text was updated successfully, but these errors were encountered: