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

Remove outdated guidance on missing analysis #1081

Merged
merged 1 commit into from May 19, 2022
Merged

Conversation

marcogario
Copy link
Contributor

As of December 2021, we do not return missing base analysis anymore. Instead on the PR that introduces code scanning, we will report all alerts as new.

We can still report a missing after, especially when we deal with outdated configurations, but that should happen significantly less often (and was also not originally explained in this paragraph).

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.

As of December 2021, we do not return missing base analysis anymore.
@marcogario marcogario requested a review from a team as a code owner May 17, 2022 10:06
README.md Show resolved Hide resolved
@aeisenberg
Copy link
Contributor

Thanks for this PR.

Does this mean that the docs should be updated as well?

@marcogario
Copy link
Contributor Author

Does this mean that the docs should be updated as well?

Yes, I have an open issue on the docs repo for this (backlinked). Waiting for it to be picked-up by their First Responder.

@marcogario marcogario merged commit f0705a6 into main May 19, 2022
@marcogario marcogario deleted the clarify_missing_base branch May 19, 2022 06:32
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

3 participants