-
Notifications
You must be signed in to change notification settings - Fork 4k
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
chore(prlint): trigger pr linter from pr reviews #26535
Conversation
Co-authored-by: Momo Kornher <mail@moritzkornher.de>
@@ -25,8 +68,8 @@ jobs: | |||
statuses: read | |||
issues: read | |||
runs-on: ubuntu-latest | |||
needs: download-if-workflow-run |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Doesn't this mean download-if-workflow-run
always has to run and complete?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
yes but as far as i can tell, in order to get an output from a previous step you must depend on that step
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
so right now if its not a workflow run i skip all individual steps of download-if-workflow-run
(but do not skip the job)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@kaizencc Can you add the README entry?
Co-authored-by: Momo Kornher <mail@moritzkornher.de>
AWS CodeBuild CI Report
Powered by github-codebuild-logs, available on the AWS Serverless Application Repository |
Thank you for contributing! Your pull request will be updated from main and then merged automatically (do not update manually, and be sure to allow changes to be pushed to your fork). |
This ends up being a lot of work. Essentially, the
pull_request_review
trigger runs the action on the merge branch which does not have the necessary secrets. This workflow has been inspired from github docs on what to do in this situation.The PR linter takes the commit sha and pr number from the
pull_request_target
workflow and assumes that those values are available. So we will take those values frompull_request_review
, upload them as artifacts and then download them when the pr linter action is triggered by the workflow run.The code in
index.ts
hasn't been tested, but should work.By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license