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

Confusion over RefSpec #32

Closed
DeadlySurgeon opened this issue Apr 18, 2020 · 4 comments
Closed

Confusion over RefSpec #32

DeadlySurgeon opened this issue Apr 18, 2020 · 4 comments
Labels
question Further information is requested stale Issues/PRs that are marked for closure due to inactivity

Comments

@DeadlySurgeon
Copy link

RefSpec is a mapping from local branches to remote references. The format of the refspec is an optional +, followed by :, where is the pattern for references on the remote side and is where those references will be written locally. The + tells Git to update the reference even if it isn’t a fast-forward. eg.: "+refs/heads/:refs/remotes/origin/"

Shouldn't src be on the local side not remote? And shouldn't dst be where the remote is written? The example also hints at that. This in context to git.PushOptions.

@DeadlySurgeon
Copy link
Author

Also this kind of tripped me up until I read more about RefSpecs on git-svm.com, but when pushing refspecs it looks more like refs/heads/<branch>:refs/heads/<branch> instead of refs/heads/<branch>:refs/remotes/origin/<branch>.

@mcuadros mcuadros added the question Further information is requested label Apr 23, 2020
@mangalaman93
Copy link

Took me forever to figure this out. Thanks for the comment.

@DeadlySurgeon
Copy link
Author

Took me forever to figure this out. Thanks for the comment.

Glad you got a resolution.

@github-actions
Copy link

To help us keep things tidy and focus on the active tasks, we've introduced a stale bot to spot issues/PRs that haven't had any activity in a while.

This particular issue hasn't had any updates or activity in the past 90 days, so it's been labeled as 'stale'. If it remains inactive for the next 30 days, it'll be automatically closed.

We understand everyone's busy, but if this issue is still important to you, please feel free to add a comment or make an update to keep it active.

Thanks for your understanding and cooperation!

@github-actions github-actions bot added the stale Issues/PRs that are marked for closure due to inactivity label Sep 30, 2023
@github-actions github-actions bot closed this as not planned Won't fix, can't repro, duplicate, stale Oct 30, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
question Further information is requested stale Issues/PRs that are marked for closure due to inactivity
Projects
None yet
Development

No branches or pull requests

3 participants