feat: inherit shared dev tooling from cr-upstream-repo #2
Reference in New Issue
Block a user
Delete Branch "feat/cr-upstream-repo-sync"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Summary
.common-repo-upstream.yamlconsumer config to sync shared dev tooling fromcommon-repo/cr-upstream-repo.pre-commit-config.yaml(trailing whitespace, EOF fixer, YAML check, merge conflict check, large file check)src/sync-check CI with upstream CI (pre-commit lint + common-repo validate)common-repo-checkworkflow to detect upstream updatesUses a separate config file because source and consumer operations can't coexist in one
.common-repo.yamlwithout leaking upstream files to downstream consumers. Tracked for native support: common-repo/common-repo#253Test plan
common-repo validate --config .common-repo-upstream.yamlpassescommon-repo apply --config .common-repo-upstream.yamlsyncs expected filescommon-repo validate(source config) still works unchangedcommon-repo-checkworkflow runs on schedule/dispatch🤖 Generated with Claude Code