Merged
Conversation
This adds a new GitHub Actions workflow that runs after a successful production release and automatically tags linked Linear issues with the release version label. Components: - scripts/tagLinearIssuesWithRelease.mjs: Script that parses the changelog to find PR numbers, queries Linear API for issues linked via GitHub attachments, and adds a version label to those issues - .github/workflows/tag-linear-issues.yml: Workflow that triggers after the release workflow completes and runs the tagging script Required secrets: - LINEAR_API_KEY: Linear API key with write access - LINEAR_TEAM_ID: Linear team identifier (e.g., 'SOU') Closes SOU-535 Co-authored-by: Michael Sukkarieh <msukkari@users.noreply.github.com>
|
Cursor Agent can help with this pull request. Just |
Contributor
|
Caution Review failedThe pull request is closed. WalkthroughAdds a new GitHub Actions workflow that runs after the production release, extracts the released version from CHANGELOG.md, and runs a Node.js script which queries the Linear GraphQL API to find issues referenced by PRs for that version and applies a v label to them. Changes
Sequence Diagram(s)sequenceDiagram
participant GA as GitHub Actions
participant Changelog as CHANGELOG.md
participant Script as Tagging Script
participant Linear as Linear GraphQL API
GA->>Changelog: Extract version
Changelog-->>GA: Return version
GA->>Script: Run script with version & creds
Script->>Changelog: Parse PR numbers for version
Changelog-->>Script: Return PR list
Script->>Linear: Query attachments for each PR URL
Linear-->>Script: Return linked issues
Script->>Script: Deduplicate issues
Script->>Linear: Get team ID by key
Linear-->>Script: Return team ID
Script->>Linear: Find or create v<version> label
Linear-->>Script: Return label ID
Script->>Linear: Add label to each issue
Linear-->>Script: Confirm updates
Script-->>GA: Report completion
Estimated code review effort🎯 3 (Moderate) | ⏱️ ~25 minutes ✨ Finishing Touches
🧪 Generate unit tests (beta)
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 |
This comment has been minimized.
This comment has been minimized.
Co-authored-by: Michael Sukkarieh <msukkari@users.noreply.github.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
2 participants
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.
Adds a GitHub Action to automatically tag Linear issues with the release version when a new release is published.
The current workflow closes Linear issues upon PR merge, but the associated changes are not live until a release. This PR introduces a mechanism to apply a release version tag to Linear issues, providing better visibility into when a fix or feature is actually deployed.
Linear Issue: SOU-535
Summary by CodeRabbit