Support for remote management in git

[Omkar Manjrekar (manjrekarom)]

Added options for adding and removing remotes.

[Microsoft Contribution License Agreements (msftclas)]

All CLA requirements met.

[Bruno Alexandre (balexandre)]

Omkar Manjrekar (@manjrekarom) if it's not much to ask, can you add "Prune/Purge Remote Branches" option as well ?

git remote prune <remote_name>

[Omkar Manjrekar (manjrekarom)]

Bruno Alexandre (@balexandre) Yes. I will be happy to add that as well. But do I need to get a confirmation first?

João Moreno (@joaomoreno) Should I create a different pull request or add it here? Sorry, I am kinda new to this stuff. Thanks!

[Bruno Alexandre (balexandre)]

Omkar Manjrekar (@manjrekarom) that will depend if there's more than one remote, and you only prune the one set as upload stream...

would be useful to have it as well, like git fetch to continue in the background and purge it time to time, as all it does is remote the remotes, not local branchs ... organizations tend to have the remote clean up time to time, and I'm facing that every time they simply forget :)

I also use this snipped to get all remotes from each author (so I know what they need to clean up)

git for-each-ref --format='%(committerdate)%09%(authorname)%09%(refname)' | sort -k5n -k2M -k3n -k4n | grep remotes | awk -F "\t" '{ printf "%-32s %-27s %s\n", $1, $2, $3 }'

[João Moreno (joaomoreno)]

Feel free to add that to this PR

[Jon Gallant (jongio)]

Omkar Manjrekar (@manjrekarom) - would love to see this get implemented. Are you still working on it? Need help?

[Omkar Manjrekar (manjrekarom)]

Jon Gallant (@jongio) I am almost forgot about that. Will start working on the purge/prune thing. I'll let you know if I need any help. Thanks for asking.

[Jon Gallant (jongio)]

Omkar Manjrekar (@manjrekarom) What are your thoughts on doing it as a separate PR instead of merging it with this one… That way we can get the baseline remote stuff in there and then add prune later on?

[Omkar Manjrekar (manjrekarom)]

Jon Gallant (@jongio) Yeah. That is fine to me. Priority stuff should be added first.

I've done add and remove remote. Can you tell me what more should go into the baseline?

[Jon Gallant (jongio)]

How about adding a command to view the remotes - git remote -v and then that hows the remote in the dropdown or output pane?

[Omkar Manjrekar (manjrekarom)]

Jon Gallant (@jongio) Yes, I'll add that in this PR.

Here is a list of all remote things from git scm. I've tried categorising them. Let me know what you think.

Baseline:

1. git remote [-v | --verbose]
2. git remote rename

Extra

1. git remote set-head (-a | --auto | -d | --delete | )
2. git remote set-branches [--add] …​
3. git remote get-url [--push] [--all]
4. git remote set-url [--push] []
5. git remote set-url --add [--push]
6. git remote set-url --delete [--push]
7. git remote [-v | --verbose] show [-n] …​
8. git remote prune [-n | --dry-run] …​
9. git remote [-v | --verbose] update [-p | --prune] [( | )…​]

[Jon Gallant (jongio)]

Omkar Manjrekar (@manjrekarom) -

[kinghat (kinghat)]

Here is a list of all remote things from git scm. I've tried categorising them. Let me know what you think.

Baseline:

1. git remote [-v | --verbose]
2. git remote rename

Extra

1. git remote set-head (-a | --auto | -d | --delete | )
2. git remote set-branches [--add] …​
3. git remote get-url [--push] [--all]
4. git remote set-url [--push] []
5. git remote set-url --add [--push]
6. git remote set-url --delete [--push]
7. git remote [-v | --verbose] show [-n] …​
8. git remote prune [-n | --dry-run] …​
9. git remote [-v | --verbose] update [-p | --prune] [( | )…​]

Omkar Manjrekar (@manjrekarom) would these be the main ones to be added?
git remote add upstream, git fetch upstream, and git rebase upstream/master or git merge upstream/master

[Jon Gallant (jongio)]

Great point. It would be awesome if I could have a 'rebase with remote' feature, but I think that is prob a diff PR.

[darkyuhoo01]

Jon Gallant (@jongio) Yes, I'll add that in this PR.

Here is a list of all remote things from git scm. I've tried categorising them. Let me know what you think.

Baseline:

git remote [-v | --verbose]
git remote rename
Extra

git remote set-head (-a | --auto | -d | --delete | )
git remote set-branches [--add] …​
git remote get-url [--push] [--all]
git remote set-url [--push] []
git remote set-url --add [--push]
git remote set-url --delete [--push]
git remote [-v | --verbose] show [-n] …​
git remote prune [-n | --dry-run] …​
git remote [-v | --verbose] update [-p | --prune] [( | )…​]

[darkyuhoo01]

Omkar Manjrekar (@manjrekarom) - would love to see this get implemented. Are you still working on it? Need help?

[João Moreno (joaomoreno)]

Apart from the error of sanitizing the remote URL, looks great, thanks!

[Jon Gallant (jongio)]

Awesome! Rachel Macfarlane (@RMacfarlane) - It would be awesome to see how we integrate the PR extension docs with this update.

[alexanderlsmith123]

Yeah this is awesome

[Omkar Manjrekar (manjrekarom)]

Thank you so very much everyone! :D Delighted to see my PR go into master. I started working on this as a Hacktoberfest task and never imagined it would go this way. This will be my first (real) accepted PR. And that too for something that I and millions of people enjoy using daily. Thanks again.

[Jon Gallant (jongio)]

Omkar Manjrekar (@manjrekarom)

That’s awesome. Thank you so much for the effort.