Remove stale competitive.md references from repo docs#169
Merged
Conversation
Remove stale competitive.md references from products README, root repository map, and messaging impact map. Competitive positioning belongs in private execution systems per content-governance, not in this public repository. Co-authored-by: Cursor <cursoragent@cursor.com>
Contributor
New File Governance CheckNo added markdown files detected. Doc Coverage CheckNo new markdown docs detected. Duplicate Detector
No significant overlap detected. Manual waiver commands (maintainers)
Waiver JSON is stored in a hidden PR comment ( Triggered by |
Contributor
Messaging Smart SuggestionsNo suggestion candidates were generated for this PR. Triggered by |
Contributor
Messaging Impact Check
No impact rules were triggered. Manual waiver commands (maintainers):
Triggered by |
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
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.
Summary
competitive.mdreferences fromproducts/README.md, rootREADME.md, andautomation/messaging-impact-map.yml.Why
products/README.mddescribed acompetitive.mdfile per product area, but no such files exist and policy keeps competitive intel private. The impact map still flagged non-existent paths, which added noise to Impact Check suggestions.Test plan
competitive.mdreferences in tracked filesproducts/README.mdstructure guidance matches content-governanceReviewer note
Governance/doc cleanup only. MongoDB ingest PRs (#142, #143, #152) are unchanged; this is safe to merge independently of those.
Made with Cursor