Skip to content
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

Enable direct tracing the autobuild build mode by default #2353

Merged
merged 7 commits into from
Jul 10, 2024

Conversation

henrymercer
Copy link
Contributor

Merge this once we've cut the final GHES 3.14 release.

This PR removes the feature flag for using direct tracing for the autobuild build mode, thereby enabling it for GHES.

Probably the most controversial change is removing the tests that require us to have at least one feature with a minimumVersion and toolsVersion property. I did this because if no features have a toolsVersion property, we'll never hit those code paths, so it isn't that important to test them. Having a synthetic feature is an option but might create user confusion.

Merge / deployment checklist

  • Confirm this change is backwards compatible with existing workflows.
  • Confirm the readme has been updated if necessary.
  • Confirm the changelog has been updated if necessary.

…lsVersion`

If no features have a `toolsVersion` property, we'll never hit those code paths, so it isn't that important to test them.
Having a synthetic feature is an option but might create user confusion.
@henrymercer henrymercer marked this pull request as ready for review July 8, 2024 09:32
@henrymercer henrymercer requested a review from a team as a code owner July 8, 2024 09:32
Copy link
Contributor

@aeisenberg aeisenberg left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good. I'd say it's unlikely we'll ever need a minimum version feature again since we've moved to toolsVersion .

CHANGELOG.md Outdated
@@ -6,6 +6,7 @@ Note that the only difference between `v2` and `v3` of the CodeQL Action is the

## [UNRELEASED]

- Improve the reliability and performance of analyzing code when analyzing a compiled language with the `autobuild` [build mode](https://docs.github.com/en/code-security/code-scanning/creating-an-advanced-setup-for-code-scanning/codeql-code-scanning-for-compiled-languages#codeql-build-modes) on GitHub Enterprise Server. This feature is already available to GitHub.com users. [#2235](https://github.com/github/codeql-action/pull/2235)
No user facing changes.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think this line should be deleted.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks, this was a bad auto merge.

@henrymercer
Copy link
Contributor Author

@angelapwen would you mind reviewing the last couple of commits so we can get this in?

Copy link
Contributor

@angelapwen angelapwen left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yep looks good! ✨

@henrymercer henrymercer merged commit be825d5 into main Jul 10, 2024
310 checks passed
@henrymercer henrymercer deleted the henrymercer/enable-direct-tracing branch July 10, 2024 09:48
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants