| FazBrowse GitHub Viewer | Trending | | Home |
| Tools: [Download Repo ZIP] [Original HTTPS Page] |
There was a problem hiding this comment.
I think this is good and should work. Two minor comments.
However, I think we should add some tests here. The logic is a bit complex and it would be good to make sure the messages are emitted only when we expect them to be.
Sorry, something went wrong.
| ) | ||
| ) { | ||
| logger.warning( | ||
| `Uploading multiple CodeQL runs with the same category is deprecated ${deprecationWarningMessage}. Please update your CodeQL CLI version or update your workflow to set a distinct category for each CodeQL run. For more information, see https://github.blog/changelog/2024-05-06-code-scanning-will-stop-combining-runs-deprecation-notice`, |
There was a problem hiding this comment.
Is this the same message as above? If so, probably best to extract to a variable so we don't accidentally change one but not the other.
Sorry, something went wrong.
There was a problem hiding this comment.
No, the message is not exactly the same. I'll extract the last part ("For more information, see ..."), but the other parts of the message are different. The first message is for third-party tools, while the second message is more specific to CodeQL-only uploads.
Sorry, something went wrong.
There was a problem hiding this comment.
Makes sense to me! Just a small comment on top of Andrew's.
Sorry, something went wrong.
|
Thanks for the reviews!
I've added tests for the (renamed) shouldShowCombineSarifFilesDeprecationWarning function which tests that this function only returns true when all conditions are met. Since this is called before showing the message, this should ensure that we never show the message inadvertently. |
Sorry, something went wrong.
There was a problem hiding this comment.
Looks good, just a comment about the warning for CodeQL.
Sorry, something went wrong.
There was a problem hiding this comment.
Looks good to me to merge once the changelog post is out.
Sorry, something went wrong.
I think we can actually merge this before the changelog post is out since the deprecation message is behind a feature flag. Does that make sense, or do you think it would be better to wait? |
Sorry, something went wrong.
|
Ah perfect, just make sure the changelog's out before you start rolling out the feature flag then! Thanks! |
Sorry, something went wrong.
There was a problem hiding this comment.
LGTM. Thanks for addressing my comments.
Sorry, something went wrong.
There was a problem hiding this comment.
Not that you needed this third approval but providing it anyway 😆
Sorry, something went wrong.
| Back | FazBrowse Home | New Git URL |
This adds a deprecation warning for merging SARIF files with non-unique categories. This is behind a feature flag.
These are the criteria for showing the deprecation warning:
Merge / deployment checklist