You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi! Thanks for Kaneo. I'm currently evaluating it as an alternative to Linear, and the self-hosted + MCP approach is exactly what I'm after.
The main thing I'd want before fully switching is Linear's development workflow around pull requests, not just issues. Specifically:
Copy branch name from a task — a one-click button that gives a ready-to-use branch name like user/ROA-42-add-bulk-download, so the branch is tied to the task by convention.
Auto-link PRs to the task — when a branch/PR with that task ID is opened, it shows up on the card (with a link).
PR status on the card — open / merged / closed reflected on the task.
Auto-move/close the task when the PR merges.
From what I can see, the GitHub integration today is issue-centric (import/sync/close issues) rather than PR/branch-centric. Is a PR-linking workflow like this something you'd consider, or already on the radar?
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
Hi! Thanks for Kaneo. I'm currently evaluating it as an alternative to Linear, and the self-hosted + MCP approach is exactly what I'm after.
The main thing I'd want before fully switching is Linear's development workflow around pull requests, not just issues. Specifically:
From what I can see, the GitHub integration today is issue-centric (import/sync/close issues) rather than PR/branch-centric. Is a PR-linking workflow like this something you'd consider, or already on the radar?
All reactions