-
Notifications
You must be signed in to change notification settings - Fork 84
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
only supports being run on "[pull_request]" #6
Comments
I'd like to support push workflows here too. FWIW, when your PR goes through multiple iterations, you can see the history of each commit's builds by looking at Github's "edit history" for the size action comment. It holds a log of every size delta produced, each compared to the PR base. To me this seems preferable, since I rarely want to see each commit's delta from the previous commit. |
Hmm, I think I misunderstood how the |
Thanks for the quick response! |
Thanks for the cool action!
I tried adding it on my existing push-triggered workflow, and got a confusing error on my first try:
Looking into the code, it appears to be because the action depends on
context.payload.pull_request
:compressed-size-action/action.js
Line 23 in 6cd4d74
which presumably doesn't exist on push-triggered workflows.
I wanted the action run on push because a PR can go through multiple iterations and I wanted the compressed size reported for every iteration.
Ideal would be to support both types of triggers (it appears there is some commented out code to use the octokit API to fetch PR data), but at the very least it would be nice to fail a bit more gracefully (with a clearer error message).
The text was updated successfully, but these errors were encountered: