cupcicm / opp Goto Github PK

I seem to remember using a competing product (that was possibly implemented in Python), and it would reset the local branch after creating a PR.

For example, if you could add a commit on your local copy of the main branch (which was the same as origin/main), then run opp pr, and this would create the PR branch and reset your local main branch to origin/main.

Is the lack of this behavior in opp intentional?

With opp, I find that I need to always manually reset my main branch after running opp pr so that I can start working on a new, unrelated feature.

Say you have 1 commits off the main branch and you run opp pr. It currently creates a new local branch, pushes it, and creates a new pull request. The expectation is that it also checks out the new local branch I think.

When contributing to a repo that you don't have write access on (e.g. cupcicm/opp in my case), you typically have a Github fork of the repo and make feature branches in your own fork (because you don't have push acccess on the origin repo), and then create a PR on the repo that you forked from.

It seems that this flow doesn't work with opp, because it doesn't allow having two remote repos configured (which I guess makes sense, because it needs to be able to choose a remote to interact with).

When making PRs on opp I need to think of branch names and interact with the Github UI, which is is obviously a horrible experience.

It would be great if we could have a way of using opp with forked repos, possibly by just using the remote named upstream if there are multiple remotes (e.g. origin and upstream).