Draft
Conversation
Captures pilot findings from the Creators team rollout so the next team adopting Linear Releases does not have to rediscover gotchas (keyword prefixes, fetch-depth, action versioning, SHA pinning). Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
Jetpack Cloud Live (direct link)
Automattic for Agencies Live (direct link)
Dashboard Live (dotcom) (direct link)
|
…dd beta note - Pipeline access key, not Personal API key - Keyword prefix finding is observed behavior from pilot (v0.5.0), not definitive - Linear Releases is in public beta - Release creation is conditional on matching commits Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
2 tasks
The Release CLI detects issues via PR references in squash merge commits, not just commit message keywords. Keyword prefixes are only needed for commits without an associated PR. Confirmed by Linear engineer in Slack. Co-Authored-By: Claude Opus 4.6 <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.
Part of #109467
Proposed Changes
Why are these changes being made?
Follow-up to the Creators Linear Release workflow PR. The pilot surfaced several gotchas (keyword prefix requirements, fetch-depth, action versioning confusion, SHA pinning) that every adopting team will hit. This doc saves them the archaeology.
Testing Instructions
Pre-merge Checklist
Co-Authored-By: Claude Opus 4.6 noreply@anthropic.com