Fails to udpate local project when working on a local branch
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 35/100
Research direction
Start in divio_cli/localdev/main.py around line 618, where the origin remote is hardcoded. Trace how the local branch and its upstream remote are determined, then review the behavior when no remote exists. Done means local branches use their upstream remote when available and otherwise ask for confirmation instead of failing.
Written by the indexing model from the issue text.
Description
Somewhat common usecase is to work on feature branches, that may or may not be present on origin remote, but might be present on different remote.
Currently 'origin' is hardcoded https://github.com/divio/divio-cli/blob/master/divio_cli/localdev/main.py#L618
It would be great to have it pull from the set upstream remote or in case it's not on any remote yet ask for a confirmation to approve continuing instead of failing
- Dominant language
- Python
- Stars
- 23
- Forks
- 19
- PR merge metrics
- No merged PRs in 30d
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.
More from divio/divio-cli
-
Difficulty 4/5 3-5 days Newbie friendliness 35/100
-
Difficulty 3/5 1-2 days Newbie friendliness 50/100
-
Difficulty 3/5 1-2 days Newbie friendliness 45/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 52/100
-
Difficulty 3/5 1-2 days Newbie friendliness 35/100
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 74/100