Skip to content

Handle remotes that are not named "origin" #48

New issue
New issue
Open
Open
Handle remotes that are not named "origin"#48
Labels
importance: 1 - must haveMust be implemented for the product to be completeurgency: 2 - we can waitwork type: implementationA task that primarily involves bashing code
Milestone
Launch
@taneliang

Description

@taneliang
taneliang
opened on Aug 15, 2020

"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.

Metadata

Metadata

Assignees

No one assigned

    Labels

    importance: 1 - must haveMust be implemented for the product to be completeurgency: 2 - we can waitwork type: implementationA task that primarily involves bashing code

    Projects

    No projects

    Milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions