| FazBrowse GitHub Viewer | Trending | | Home |
| Tools: [Download Repo ZIP] [Original HTTPS Page] |
There was a problem hiding this comment.
This PR adds documentation to the README about keeping the CodeQL Action up to date. The new section provides guidance on version pinning strategies and warns about potential functionality loss when using pinned versions with server-side feature flag changes.
Changes:
Sorry, something went wrong.
There was a problem hiding this comment.
LGTM!
Sorry, something went wrong.
|
|
||
| ## Keeping the CodeQL Action up to date | ||
|
|
||
| We recommend referencing the CodeQL Action using a major version tag (e.g. `v3`) in your workflow file. This ensures your workflow automatically picks up the latest release within that major version, including bug fixes, new features, and updated CodeQL CLI versions. |
There was a problem hiding this comment.
This should be v4 now.
Sorry, something went wrong.
|
|
||
| If you pin to a specific commit SHA or patch version tag, ensure you keep it updated (e.g. via [Dependabot](https://docs.github.com/en/code-security/dependabot/working-with-dependabot/keeping-your-actions-up-to-date-with-dependabot)). Some CodeQL Action features are controlled by server-side flags that may be removed over time, which can cause pinned versions to lose functionality. | ||
|
|
||
|
|
There was a problem hiding this comment.
Minor: extra empty line?
Sorry, something went wrong.
| Back | FazBrowse Home | New Git URL |
Summary