| FazBrowse GitHub Viewer | Trending | | Home |
| Tools: [Download Repo ZIP] [Original HTTPS Page] |
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
| Back | FazBrowse Home | New Git URL |
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.
Choose a reason Spam Abuse Off Topic Outdated Duplicate Resolved Low QualityHaving this trigger on all pushes is useful for catching problems where folks edit a TS file and push it to a branch to do some testing, but forget to compile the Action. This failing check is then be a useful indicator to help resolve why their intended behaviour wasn't occurring.
Sorry, something went wrong.
Uh oh!
There was an error while loading. Please reload this page.
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.
Choose a reason Spam Abuse Off Topic Outdated Duplicate Resolved Low QualityThat seems like a very niche use case that comes at the cost of a lot of extra runs and confusion. For testing, I'd suggest opening a draft PR that triggers the checks instead of relying on push triggers.
If you feel strongly that this is a useful behaviour though, then I'd suggest we split out the relevant checks from this workflow (possibly as a reusable workflow) that is called by a workflow with a different name that runs on push and this one.
Sorry, something went wrong.
Uh oh!
There was an error while loading. Please reload this page.