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

Merge main into v1 #522

Closed
wants to merge 25 commits into from
Closed

Merge main into v1 #522

wants to merge 25 commits into from

Conversation

github-actions[bot]
Copy link
Contributor

Merging eeaefb6 into v1

Conductor for this PR is @aibaars

Contains the following pull requests:

Please review the following:

  • The CHANGELOG displays the correct version and date.
  • The CHANGELOG includes all relevant, user-facing changes since the last release.
  • There are no unexpected commits being merged into the v1 branch.
  • The docs team is aware of any documentation changes that need to be released.
  • The mergeback PR is merged back into main after this PR is merged.

RA80533 and others added 25 commits May 7, 2021 20:15
Adds an empty changelog file and a reminder to update it when opening
pull requests.

Also, adds a 1.0.0 version number in the package.json, which is what
we _could_ use for version numbering.
Co-authored-by: Aditya Sharad <6874315+adityasharad@users.noreply.github.com>
(Adding the changelog itself.)
Fix grouping of the analysis logs, so that custom query logs also get grouped.
Capture the stdout of codeql database analyze, which contains the analysis summary
from summary and diagnostic queries.
Log this output in its own group, along with the baseline computed in the Action.
As produced by npm ci && npm run removeNPMAbsolutePaths.
Analyze: Improve log grouping and log the analysis summary in its own group
Ensure queries[language] objects are initialized
Use --additional-packs instead of --search-path
@aeisenberg
Copy link
Contributor

Looks right. This is just testing the new automated release process. Please ignore.

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.

None yet

4 participants