Clarify GCP governance metadata in glossary#14
Open
shreyaskommuri wants to merge 1 commit into
Open
Conversation
Constraint: Repository guidance keeps UCSB-specific definitions in the glossary and requires substantive edits to refresh last_reviewed. Rejected: Keep the broad labels-only wording | the tagging page distinguishes GCP Resource Manager Tags from project labels. Confidence: high Scope-risk: narrow Directive: Keep glossary definitions aligned with provider-specific guidance pages. Tested: Confirmed the old GCP labels-only wording is removed and the glossary matches docs/general/tagging.md. Not-tested: Local Jekyll build not run because the repo has no Gemfile.
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Constraint: Repository guidance keeps UCSB-specific definitions in the glossary and requires substantive edits to refresh last_reviewed.
Rejected: Keep the broad labels-only wording | the tagging page distinguishes GCP Resource Manager Tags from project labels.
Confidence: high
Scope-risk: narrow
Directive: Keep glossary definitions aligned with provider-specific guidance pages.
Tested: Confirmed the old GCP labels-only wording is removed and the glossary matches docs/general/tagging.md.
Not-tested: Local Jekyll build not run because the repo has no Gemfile.