Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Handle remotes that are not named "origin" #48

Open
taneliang opened this issue Aug 15, 2020 · 0 comments
Open

Handle remotes that are not named "origin" #48

taneliang opened this issue Aug 15, 2020 · 0 comments
Labels
importance: 1 - must have Must be implemented for the product to be complete urgency: 2 - we can wait work type: implementation A task that primarily involves bashing code
Milestone
Launch

Comments

@taneliang
Copy link
Owner

taneliang commented Aug 15, 2020 •
edited
Loading

"origin" is currently hardcoded in some places, but we need to support other remote names so that we can support the forking workflow that's common on GitHub.
@taneliang taneliang added this to the Launch milestone Aug 15, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
importance: 1 - must have Must be implemented for the product to be complete urgency: 2 - we can wait work type: implementation A task that primarily involves bashing code
Projects
None yet
Milestone
Launch
Development

No branches or pull requests
1 participant
@taneliang