Problem with new PR is made in GitHub
Open
Nobody has claimed this yet.
- Dominant language
- Elixir
- Stars
- 76
- Forks
- 7
- PR merge metrics
- No merged PRs in 30d
Description
Expected Behavior
- New PRs create in GitHub without a Linear issue ID in their name should create a new issue in Linear linked to the PR
- New PRs created with a Linear issue ID should be linked to that ID
- Comments should be synced both ways between Linear and GitHub
Current Behavior
- Creating a new PR in GitHub that is not linked to an existing Linear issue does not create a new issue.
- When linking a PR to an existing Linear issue, comments from Linear are pushed to GitHub, but comments from GitHub are not pushed to Linear.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No files or tests are named. Start by locating the GitHub pull-request synchronization entry point and the Linear issue and comment handling; reproduce both PR cases and the one-way comment sync. Done means unlinked PRs create and link a Linear issue, linked PRs remain associated, and comments sync in both directions.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- elixir
- Domain
- api, backend
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100