ci(open-knowledge): stamp Linear issues with the release they ship in (#2748)#697
Merged
Conversation
… (#2748) Add linear-release.yml: on each OK release cut, attach the Linear issues referenced in the cut's commits to a release in the OpenKnowledge scheduled pipeline and advance its stage (Beta on a beta cut, Stable + complete on a stable promotion). Triggers off the existing desktop-release repository_dispatch that release.yml and promote-stable.yml already fire, so the publish path is untouched. No-ops until the LINEAR_ACCESS_KEY pipeline access-key secret is set on inkeep/open-knowledge. GitOrigin-RevId: 7c37bdb13e02ca9fa02006cd1f05705cfd7a45f1
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.
Copybara-translated 1 Inkeep OSS change. Rebase-merge this PR so the prepared commit lands directly on public main.