Bug: View does not indicate necessary actions after rebase
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 569
- Forks
- 43
- PR merge metrics
- No merged PRs in 30d
Description
When I locally rebase my stack on the main branch, e.g. main branch has some new commits which should be included in my stack, I have to force push my branch(es) to remote. I therefore perform the following actions:
git rebase mainstack-pr viewstack-pr submit
The force pushes arrive on the remote and the eventual result works. However, the 2nd step/view does not show any necessary action. What I would like is some indicator that the stack has to be submitted again because of a different/newer base.
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
Reproduce the workflow with git rebase main, stack-pr view, and stack-pr submit, focusing on the missing indication after the rebase. Trace the stack-pr view and stack-pr submit entry points to determine how base differences are detected; done means view clearly signals when the stack must be submitted again.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- cli
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100