-
Notifications
You must be signed in to change notification settings - Fork 283
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
Build adjustments for code annotation #2155
base: master
Are you sure you want to change the base?
Conversation
.github/workflows/main.yml
Outdated
on: | ||
push: | ||
pull_request: | ||
types: [opened] |
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.
This will cause subsequent builds to not trigger for PRs. This should not be the case and the default types for pull_request
is opened
, syncronize
, reopened
which all handle different cases with pushes to the pull request for commits and if a pull request is opened again after closing. Best is to revert this change as you want it to build for each time something happens to the commit tree for the PR.
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.
Hmm, when testing on my fork the push
trigger was firing whenever I made a commit to my draft PR. That could've been something on my end - I'll revert this portion though just to be safe.
7b82c94
to
95d7f9a
Compare
This PR overrides Nuke's log handling and removes the problematic formatting the default analyzers were unable to process as well as improving the build flow to reduce duplicate warnings (and thus annotations). Building and testing have merged into a single step, and warnings are suppressed from the test rebuild since they're just refired from the initial build process anyway.
In addition, I adjusted the workflow so pushes to an existing pull request won't trigger both the push and PR builds to occur in some cases which also contributed to the warning duplication. In the end, file changes now have code-level annotations!