Skip to content

allow fetch to receive a ref option #361

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
Closed
taquitos opened this issue Apr 19, 2018 · 3 comments
Closed

allow fetch to receive a ref option #361

taquitos opened this issue Apr 19, 2018 · 3 comments

Comments

@taquitos
Copy link
Contributor

taquitos commented Apr 19, 2018 •
edited
Loading

It would be 💯 if we could allow fetch to receive a ref option
One example of why it's useful:
When interacting with GitHub pull requests, you need to specify a ref:
git fetch origin pull/20/head
This fetches a branch associated with a PR
@taquitos taquitos mentioned this issue Apr 19, 2018
Merged
@stale
Copy link

stale bot commented Jun 18, 2018

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

@stale stale bot added the wontfix label Jun 18, 2018
@taquitos
Copy link
Contributor Author

It's been a busy few months, and I've forked the repo so we can continue moving forward. I'll try to update this soon

@stale stale bot removed the wontfix label Jun 18, 2018
perlun pushed a commit that referenced this issue Jun 25, 2018
@taquitos @perlun
Allow fetch operation to receive a ref param (#362)
e7f1880 
* Allow fetch operation to receive a `ref` param
addresses #361

* Update remote object

* remove .ruby-version

* Use options instead of separate param

* Update for comments

* Update for style
@taquitos
Copy link
Contributor Author

Merged pr

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@taquitos