-
Notifications
You must be signed in to change notification settings - Fork 477
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
feat(ci): linear issues sync #2562
base: main
Are you sure you want to change the base?
Conversation
* Add linear-sync tool to update Linear issues when a release is created * Sync with changelog library to extract PRs between releases * Add sync_linear job to GitHub Actions release workflow * Update Linear issues to "Released" state when code is released * Extract Linear issue IDs from PR bodies and branch names * Add release date and version comments to Linear issues
✅ Deploy Preview for vcluster-docs canceled.
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm not going to be able to review the rest, but had that one question.
- uses: actions/checkout@v4 | ||
- uses: actions/setup-go@v5 | ||
with: | ||
go-version-file: go.mod |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
When comparing this with loft-enterprise, why is this go.mod and that one is go.work?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We are not using go workspaces
in this repository. This is just a way for the action to retrieve the go version
to be installed from the file.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks like this is pre-existing in platform, so i just skimmed code and compared to platform. Workflow changes look ok. Overall lgtm.
What issue type does this pull request address? (keep at least one, remove the others)
/kind enhancement
What does this pull request do? Which issues does it resolve? (use
resolves #<issue_number>
if possible)References OPS-94
Please provide a short message that should be published in the vcluster release notes
Fixed an issue where vcluster ...
What else do we need to know?
Notes for PR review in Linear issue.