Backport of docs: Update automated license reporting topic into stable-website #3596
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
hc-github-team-secure-boundary
force-pushed
the
backport/dheath-elur-edits/seriously-possible-crayfish
branch
from
1f57896
to
8fe2533
Compare
hc-github-team-secure-boundary
force-pushed
the
backport/dheath-elur-edits/seriously-possible-crayfish
branch
from
8fe2533
to
1f57896
Compare
Dan-Heath
approved these changes
Aug 16, 2023
Dan-Heath
deleted the
backport/dheath-elur-edits/seriously-possible-crayfish
branch
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Backport
This PR is auto-generated from #3595 to be assessed for backporting due to the inclusion of the label backport/website.
WARNING automatic cherry-pick of commits failed. Commits will require human attention.
The below text is copied from the body of the original PR.
The language on the automated license utilization reporting topic is carefully controlled. The PM has asked that we make a minor update to bring the Boundary topic in line with the changes that were applied in Vault PR #22026.
The Vault PR has minor wording updates on lines #58 and #195, but these were already applied to the existing Boundary topic in PR #3491:
Line #58:
Line #195:
Therefore, this PR contains only the remaining minor text change on line #25 from the Vault PR.