Resuming development on a different machine?
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 569
- Forks
- 43
- PR merge metrics
- No merged PRs in 30d
Description
After using stack-pr submit from one machine, I need to resume development work on a different machine now.
What is the best way to do this?
Do I need to git checkout each remote branch for each PR in the stack, so they are all available locally on my new machine? Even after doing that, will stack-pr have sufficient metadata to operate on this new stack (my understanding is all the metadata is in the commit history, so it should work)?
Contributor guide
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
Start with the stack-pr submit workflow and trace how a stack is discovered after work moves to another machine. Check how remote branches and commit-history metadata are used, then document the required setup and verify it against the normal stacked-PR workflow. Done means a newcomer can resume development without guessing which branches or metadata to restore.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- cli, tooling
- Issue type
- Documentation
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100