docs(compute-plane): link decision 0001 instead of inlining the rationale - #57
docs(compute-plane): link decision 0001 instead of inlining the rationale#57myasnikovdaniil wants to merge 1 commit into
Conversation
…nale The "Revision (this PR)" field carried a paragraph explaining why the preset-field revision was set aside. Post-merge "this PR" no longer refers to anything, and the Overview restates the same material, so the field was a third copy of the rationale with no home of its own. Decision 0001 is that home now. Replace the field with Supersedes plus a link. Assisted-By: Claude <noreply@anthropic.com> Signed-off-by: Myasnikov Daniil <myasnikovdaniil2001@gmail.com>
|
Important Review skippedAuto reviews are disabled on base/target branches other than the default branch. Please check the settings in the CodeRabbit UI or the ⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Pro Plus Run ID: You can disable this status message by setting the Use the checkbox below for a quick retry:
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
The field held a whole paragraph on why the preset-field revision was set aside. "This PR" stops resolving the moment the next revision lands, so it was unmaintainable by construction, and Overview directly below it already said the same thing — a third copy of one rationale with no place of its own. Decision 0001 is that place now, so the field becomes Supersedes plus a link. This was #57, stacked on this branch. Folded here instead: the change is one line in a file this branch already edits, so a separate stacked pull request bought nothing and needed a rebase to survive the move of the records directory. Assisted-By: Claude <noreply@anthropic.com> Signed-off-by: Myasnikov Daniil <myasnikovdaniil2001@gmail.com>
|
Folded into #56, it was one line in a file that branch already touches. |
The field held a whole paragraph on why the preset-field revision was set aside. "This PR" stops resolving the moment the next revision lands, so it was unmaintainable by construction, and Overview directly below it already said the same thing — a third copy of one rationale with no place of its own. Decision 0001 is that place now, so the field becomes Supersedes plus a link. This was #57, stacked on this branch. Folded here instead: the change is one line in a file this branch already edits, so a separate stacked pull request bought nothing and needed a rebase to survive the move of the records directory. Assisted-By: Claude <noreply@anthropic.com> Signed-off-by: Myasnikov Daniil <myasnikovdaniil2001@gmail.com>
The field held a whole paragraph on why the preset-field revision was set aside. "This PR" stops resolving the moment the next revision lands, so it was unmaintainable by construction, and Overview directly below it already said the same thing — a third copy of one rationale with no place of its own. Decision 0001 is that place now, so the field becomes Supersedes plus a link. This was #57, stacked on this branch. Folded here instead: the change is one line in a file this branch already edits, so a separate stacked pull request bought nothing and needed a rebase to survive the move of the records directory. Assisted-By: Claude <noreply@anthropic.com> Signed-off-by: Myasnikov Daniil <myasnikovdaniil2001@gmail.com>
Stacked on #56, base is
docs/decisions-log.compute-plane proposal metadata carries a
Revision (this PR):field holding a whole paragraph about why the preset-field revision was set aside. After merge "this PR" points at nothing, and Overview right below already says the same thing, so it was a third copy of the same rationale with no place of its own.Decision 0001 from #56 is that place now, so the field becomes
Supersedes:plus a link.Andrei Kvapil (@kvaps) it is your proposal, please check I did not drop anything you want kept in the header.