Repository navigation
feat(protocol): check the working-fork route before implementation (v0.11.0) - #316
Merged
Merged
Conversation
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
Relates to #56. The VictoriaLogs and yottacode research cases produced integrated target diffs before their working-fork routes were established. Make the route check an explicit step before expanding a local experiment into a target implementation.
opensiro-contributionsroute early. Record the verified destination or the blocker in the existing case.v0.11.0on top of feat(protocol): require explicit owner consent before third-party public outreach (v0.10.0) #315. Preserve exact per-action approval for external public communication, including publicly visible fork-local PRs. The early route check is read-only.Validation