Args for `git pull` - not just clone about caddy-git HOT 6 CLOSED

I don't wanna introduce a breaking change, would've just changed to more specific clone_args and pull_args while removing args.

from caddy-git.

It has been implemented and should show up in Caddy soon.

from caddy-git.

Good point you've raised there, though the document indicates the args are for clone.

How does changing pull to fetch and checkout help your scenario ?

from caddy-git.

Yes, the documentation's good @abiosoft, sorry I should have been more clear, but I meant when reading code it's not clear unless familiar with the particular argument used.

pull attempts a merge in the presence of local changes; if it instead fetched (without moving HEAD) and then checkouted the remote copy, local changes would be lost in favour of remote, just as with pull -X theirs.

My goal is just to ignore anything I've done tinkering around on the server, or that's been overwritten by something (presumably accidentally) and replace it with the latest revision under version control.

from caddy-git.

I wanted to --allow-unrelated-histories so that my static site which's generated and (force)-pushed to a branch works. But, of course, the arg goes to clone and not to pull

from caddy-git.

That sounds good; potentially solves some problems people might have the other way around too.

from caddy-git.