We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
When integrating with Linear, PRs now must keep track of two things:
One would expect Linear to follow this automatically, but it doesn't.
Then, we end up with Github Issues vs. Linear Issues, which is not only noisy but also cumbersome to do manually.
Implement workflow automation that will:
<!-- Closes to TS-1, TS-2, TS-N --> <!-- Part of to TS-5, TS-7, N -->
Premisses:
Docs:
The final solution must be a GitHub action that all other repos can reuse; it can go here:
The text was updated successfully, but these errors were encountered:
Thanks to @nedsalk for the ideas and discussions around this. ❤️
Sorry, something went wrong.
Closing to test out integration with linear - will reopen immediately.
nedsalk
Successfully merging a pull request may close this issue.
Problem
When integrating with Linear, PRs now must keep track of two things:
One would expect Linear to follow this automatically, but it doesn't.
Then, we end up with Github Issues vs. Linear Issues, which is not only noisy but also cumbersome to do manually.
Desires
Solution
Implement workflow automation that will:
Premisses:
Docs:
Github Action
The final solution must be a GitHub action that all other repos can reuse; it can go here:
The text was updated successfully, but these errors were encountered: