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 releases/v2 #1608

Merged
merged 15 commits into from
Mar 27, 2023
Merged

Merge main into releases/v2 #1608

merged 15 commits into from
Mar 27, 2023

Conversation

github-actions[bot]
Copy link
Contributor

@github-actions github-actions bot commented Mar 27, 2023

Merging fb32c3f into releases/v2.

Conductor for this PR is @henrymercer.

Contains the following pull requests:

Please do the following:

  • Ensure the CHANGELOG displays the correct version and date.
  • Ensure the CHANGELOG includes all relevant, user-facing changes since the last release.
  • Check that there are not any unexpected commits being merged into the releases/v2 branch.
  • Ensure the docs team is aware of any documentation changes that need to be released.
  • Approve and merge this PR. Make sure Create a merge commit is selected rather than Squash and merge or Rebase and merge.
  • Merge the mergeback PR that will automatically be created once this PR is merged.

github-actions[bot] and others added 14 commits March 22, 2023 19:04
Mergeback v2.2.8 refs/heads/releases/v2 into main
…g-override

Add override for code scanning analysis of default branch
 - The `upload` input to the `analyze` Action now accepts the following values:
    - `always` is the default value, which uploads the SARIF file to Code Scanning for successful and failed runs.
    - `failure-only` is recommended for customers post-processing the SARIF file before uploading it to Code Scanning. This option uploads debugging information to Code Scanning for failed runs to improve the debugging experience.
    - `never` avoids uploading the SARIF file to Code Scanning even if the code scanning run fails. This is not recommended for external users since it complicates debugging.
    - The legacy `true` and `false` options will be interpreted as `always` and `failure-only` respectively.

---------

Co-authored-by: Henry Mercer <[email protected]>
Only tests the property we are looking for and avoids problems with
different cross-platform behavior.
…-workaround

Work around duplicate locations bug in diagnostics export
@henrymercer henrymercer marked this pull request as ready for review March 27, 2023 10:58
@henrymercer henrymercer requested a review from a team as a code owner March 27, 2023 10:58
@henrymercer henrymercer merged commit 04df126 into releases/v2 Mar 27, 2023
@henrymercer henrymercer deleted the update-v2.2.9-fb32c3fef branch March 27, 2023 13:36
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