Repository navigation
chore(working-model): sync the block and pin the umbrella template to v1 - #5
Merged
Merged
Conversation
Two changes that must land together. The regenerated block carries the real filing rule -- component/workstream labels always, a milestone only when the work is scheduled, otherwise platform-debt and none -- matching the umbrella's canonical section 2 and the runtime digest. The block had said "milestone + labels", which reads as requiring one on every issue. The pin is what stops this recurring. This job checked out the umbrella with no ref:, i.e. its default branch resolved at CI time, so any template correction on umbrella main reddened this repo's next PR immediately. A two-line clarification cost a 9-repo flag day, which is why the block was left contradicting the canonical rule rather than fixed. Pinned to working-model-v1, umbrella main can correct the template without touching this repo, and the bump happens here on its own schedule. Split these and CI fails: new copies checked against the old template. Refs dmfdeploy/dmfdeploy#458 Signed-off-by: znerol2 <6800371+znerol2@users.noreply.github.com>
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.
Sync the working-model block and pin this repo's CI to the umbrella template
tag. Part of the coordinated rollout for dmfdeploy/dmfdeploy#458.
Two changes, one commit — deliberately
The block now states the real filing rule. It said "milestone +
component:*/workstream:*labels", which reads as requiring a milestone onevery issue. The canonical rule (umbrella
WORKING-MODEL.md§2, and the runtimedigest every session receives) is: labels always, a milestone only if the
work is scheduled, otherwise
platform-debtand none. Regenerated withcheck-working-model-sync.sh --apply— no copy hand-edited.The pin is what stops this recurring. This job checked out
dmfdeploy/dmfdeploywith noref:— its default branch, resolved at CItime — so any template correction on umbrella
mainreddened this repo's nextPR immediately. A two-line clarification cost a 9-repo flag day, which is why
the block was left contradicting the canonical rule for weeks rather than fixed.
Pinned to
working-model-v1, umbrellamaincan correct the template withouttouching this repo, and the bump happens here on its own schedule.
They cannot be split: new copies checked against the old template fail CI.
Verification
actionlintclean; block copies verified byte-identical against theworking-model-v1tag's template (not against a branch that could move).Refs dmfdeploy/dmfdeploy#458