While working on a personal project, I ran into a workflow issue:
My Linear team was mapped to the wrong GitHub repository.
Result?
New issues created from Linear were landing in the wrong repo.
Not catastrophic — but messy.
The problem
Once I identified the mapping issue, I had to clean up the already-created issues.
Manual fix would mean:
- recreating issues
- copying descriptions
- re-adding labels
- restoring references manually
That’s unnecessary operational overhead.
The solution
I used GitHub CLI to transfer the issues to the correct repository.
That preserved:
- issue history
- comments
- metadata
- workflow continuity
Fast, clean, low-risk.
Why this is useful
CLI tooling often feels optional until it saves you time.
This was a good reminder that understanding your tooling deeply helps you solve workflow problems faster and cleaner.
Even in hobby projects, good operational habits matter.
Helpful resources for getting started with GitHub CLI
GitHub CLI official docs:
https://cli.github.com/
Installation:
https://cli.github.com/manual/installation
Authentication:
https://cli.github.com/manual/gh_auth_login
Issue management:
https://cli.github.com/manual/gh_issue
Repository management:
https://cli.github.com/manual/gh_repo
Small workflow problem. Useful tooling lesson.
