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.

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

implementation/design: use upstream instead of remote name #5

Open
tmastny opened this issue Jan 8, 2020 · 0 comments
Open

implementation/design: use upstream instead of remote name #5

tmastny opened this issue Jan 8, 2020 · 0 comments

Comments

@tmastny
Copy link
Owner

tmastny commented Jan 8, 2020

Right now browse uses the remote name to build the GitHub link. It defaults to "origin" which is the typical, default name. browse also has remote name as a parameter and allows users to set a global default.

However, would it be better to use the current branch upstream? This would be consistent with git's interpretation of a "default" remote.

Key details:

git2r::repository_head() %>% git2r::branch_get_upstream()
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant