docs(sync): describe the workflow's own rule, not the branch's current state - #159
Merged
Conversation
…t state The comment asserted that main accepts changes only through a pull request. That is a property of the branch settings, not of this file, and it is not true of openadapt-ops right now. State what the workflow does: it never pushes to main, so publishing works in either configuration. Co-Authored-By: Claude Fable 5 <noreply@anthropic.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
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.
Comment-only follow-up to #157.
The block above the publish step said
mainaccepts changes only through apull request. That describes the branch settings rather than this file, and it
does not match
openadapt-opsright now: classic protection onmainwasremoved earlier today, so
GET /branches/main/protectionreturns 404.Reworded to state what the workflow itself guarantees: it never pushes to
main, so the publish path works whether or notmainrequires a pullrequest. No behaviour change.