Git/branch - Revision history

Woozle at 20:36, 30 September 2025

2025-09-30T20:36:57Z

← Older revision		Revision as of 20:36, 30 September 2025
Line 33:		Line 33:
	** Note: if the branch is not in the local repository, then you just need to [[git fetch]] it after the <code>git checkout <old_name></code>.		** Note: if the branch is not in the local repository, then you just need to [[git fetch]] it after the <code>git checkout <old_name></code>.
	** Also: {{fmt/code\|git branch -c {{arg\|new_name}}}} to copy instead of renaming.		** Also: {{fmt/code\|git branch -c {{arg\|new_name}}}} to copy instead of renaming.
			** {{fmt/code\|git push origin {{arg\|new_name}} --set-upstream}} to push up to origin and override/overwrite the connection to the local repo's ''old'' name (I think)

Woozle at 20:42, 11 June 2023

2023-06-11T20:42:34Z

← Older revision		Revision as of 20:42, 11 June 2023
Line 30:		Line 30:
	===How To===		===How To===
	* '''2019-10-07''' [https://linuxize.com/post/how-to-rename-local-and-remote-git-branch/ How To Rename a Local and Remote Git Branch]		* '''2019-10-07''' [https://linuxize.com/post/how-to-rename-local-and-remote-git-branch/ How To Rename a Local and Remote Git Branch]
	** Basically: ~~<tt>~~git branch -m {{arg\|new_name}}~~</tt>~~ renames the branch locally and doesn't mess with anything upstream. It's like you just created {{arg\|new_name}} and put stuff in it.		** Basically: {{fmt/code\|git branch -m {{arg\|new_name}}}} renames the branch locally and doesn't mess with anything upstream. It's like you just created {{arg\|new_name}} and put stuff in it.
	** Note: if the branch is not in the local repository, then you just need to [[git fetch]] it after the <code>git checkout <old_name></code>.		** Note: if the branch is not in the local repository, then you just need to [[git fetch]] it after the <code>git checkout <old_name></code>.
	** Also: ~~<tt>~~git branch -c {{arg\|new_name}}~~</tt>~~ to copy instead of renaming.		** Also: {{fmt/code\|git branch -c {{arg\|new_name}}}} to copy instead of renaming.

Woozle at 20:41, 11 June 2023

2023-06-11T20:41:16Z

← Older revision		Revision as of 20:41, 11 June 2023
Line 32:		Line 32:
	** Basically: <tt>git branch -m {{arg\|new_name}}</tt> renames the branch locally and doesn't mess with anything upstream. It's like you just created {{arg\|new_name}} and put stuff in it.		** Basically: <tt>git branch -m {{arg\|new_name}}</tt> renames the branch locally and doesn't mess with anything upstream. It's like you just created {{arg\|new_name}} and put stuff in it.
	** Note: if the branch is not in the local repository, then you just need to [[git fetch]] it after the <code>git checkout <old_name></code>.		** Note: if the branch is not in the local repository, then you just need to [[git fetch]] it after the <code>git checkout <old_name></code>.
			** Also: <tt>git branch -c {{arg\|new_name}}</tt> to copy instead of renaming.

Woozle: /* How To */

2023-06-11T19:25:41Z

How To

← Older revision		Revision as of 19:25, 11 June 2023
Line 30:		Line 30:
	===How To===		===How To===
	* '''2019-10-07''' [https://linuxize.com/post/how-to-rename-local-and-remote-git-branch/ How To Rename a Local and Remote Git Branch]		* '''2019-10-07''' [https://linuxize.com/post/how-to-rename-local-and-remote-git-branch/ How To Rename a Local and Remote Git Branch]
			** Basically: <tt>git branch -m {{arg\|new_name}}</tt> renames the branch locally and doesn't mess with anything upstream. It's like you just created {{arg\|new_name}} and put stuff in it.
	** Note: if the branch is not in the local repository, then you just need to [[git fetch]] it after the <code>git checkout <old_name></code>.		** Note: if the branch is not in the local repository, then you just need to [[git fetch]] it after the <code>git checkout <old_name></code>.

Woozle: renaming a branch

2020-01-19T15:09:47Z

renaming a branch

← Older revision		Revision as of 15:09, 19 January 2020
Line 28:		Line 28:
	** [https://git-scm.com/docs/git-branch git-branch - List, create, or delete branches]		** [https://git-scm.com/docs/git-branch git-branch - List, create, or delete branches]
	** [http://git-scm.com/book/en/v2/Git-Branching-Branches-in-a-Nutshell 3.1 Git Branching - Branches in a Nutshell]		** [http://git-scm.com/book/en/v2/Git-Branching-Branches-in-a-Nutshell 3.1 Git Branching - Branches in a Nutshell]
			===How To===
			* '''2019-10-07''' [https://linuxize.com/post/how-to-rename-local-and-remote-git-branch/ How To Rename a Local and Remote Git Branch]
			** Note: if the branch is not in the local repository, then you just need to [[git fetch]] it after the <code>git checkout <old_name></code>.

Woozle: deleting a branch

2018-09-24T12:12:49Z

deleting a branch

← Older revision		Revision as of 12:12, 24 September 2018
Line 13:		Line 13:
	* <code>git {{l/same\|checkout}} {{arg\|name}}</code> moves {{l/same\|HEAD}} to point to the branch called "name"		* <code>git {{l/same\|checkout}} {{arg\|name}}</code> moves {{l/same\|HEAD}} to point to the branch called "name"
	** Note: <code>git {{l/same\|checkout}} -b {{arg\|name}}</code> accomplishes both of the above in a single command		** Note: <code>git {{l/same\|checkout}} -b {{arg\|name}}</code> accomplishes both of the above in a single command
			* <code>git branch -d {{arg\|branch name}}</code> to delete a branch
			** Note: must be in a different branch

	The basic sequence of events for creating a new branch called "test", updating it, then reverting back to the original branch:		The basic sequence of events for creating a new branch called "test", updating it, then reverting back to the original branch:

Woozle: /* Reference */

2018-08-03T17:01:27Z

Reference

← Older revision		Revision as of 17:01, 3 August 2018
Line 23:		Line 23:
	==Links==		==Links==
	===Reference===		===Reference===
	* [http://git-scm.com/book/en/v2/Git-Branching-Branches-in-a-Nutshell 3.1 Git Branching - Branches in a Nutshell]		* Official:
			** [https://git-scm.com/docs/git-branch git-branch - List, create, or delete branches]
			** [http://git-scm.com/book/en/v2/Git-Branching-Branches-in-a-Nutshell 3.1 Git Branching - Branches in a Nutshell]

Woozle: git checkout -b

2018-05-27T16:27:05Z

git checkout -b

← Older revision		Revision as of 16:27, 27 May 2018
Line 12:		Line 12:
	* <code>git branch {{arg\|name}}</code> creates a new branch called "name", pointing at the current {{l/same\|HEAD}} revision		* <code>git branch {{arg\|name}}</code> creates a new branch called "name", pointing at the current {{l/same\|HEAD}} revision
	* <code>git {{l/same\|checkout}} {{arg\|name}}</code> moves {{l/same\|HEAD}} to point to the branch called "name"		* <code>git {{l/same\|checkout}} {{arg\|name}}</code> moves {{l/same\|HEAD}} to point to the branch called "name"
			** Note: <code>git {{l/same\|checkout}} -b {{arg\|name}}</code> accomplishes both of the above in a single command

	The basic sequence of events for creating a new branch called "test", updating it, then reverting back to the original branch:		The basic sequence of events for creating a new branch called "test", updating it, then reverting back to the original branch:

Woozle: Brief usage sketch

2015-03-13T19:45:00Z

Brief usage sketch

← Older revision		Revision as of 19:45, 13 March 2015
Line 12:		Line 12:
	* <code>git branch {{arg\|name}}</code> creates a new branch called "name", pointing at the current {{l/same\|HEAD}} revision		* <code>git branch {{arg\|name}}</code> creates a new branch called "name", pointing at the current {{l/same\|HEAD}} revision
	* <code>git {{l/same\|checkout}} {{arg\|name}}</code> moves {{l/same\|HEAD}} to point to the branch called "name"		* <code>git {{l/same\|checkout}} {{arg\|name}}</code> moves {{l/same\|HEAD}} to point to the branch called "name"

			The basic sequence of events for creating a new branch called "test", updating it, then reverting back to the original branch:
			* <code>git branch test</code> - create the branch
			* <code>git checkout test</code> - switch to it
			* {{l/sub\|stage}} whatever changes you want to include in "test"
			** This can include adding any new files you've created for this branch.
			* <code>git commit -a -m 'made a change'</code> - commit the change to "test"
			* <code>git checkout master</code> - switch back to the main branch (removes new files, restores any you deleted)
	==Links==		==Links==
	===Reference===		===Reference===
	* [http://git-scm.com/book/en/v2/Git-Branching-Branches-in-a-Nutshell 3.1 Git Branching - Branches in a Nutshell]		* [http://git-scm.com/book/en/v2/Git-Branching-Branches-in-a-Nutshell 3.1 Git Branching - Branches in a Nutshell]

Woozle: actions

2015-03-13T18:41:07Z

actions

← Older revision		Revision as of 18:41, 13 March 2015
Line 10:		Line 10:
	* <code>git branch -a</code> lists both local and remote branches		* <code>git branch -a</code> lists both local and remote branches
	Actions:		Actions:
	* <code>git branch {{arg\|name}}</code> creates a new branch called "name"		* <code>git branch {{arg\|name}}</code> creates a new branch called "name", pointing at the current {{l/same\|HEAD}} revision
			* <code>git {{l/same\|checkout}} {{arg\|name}}</code> moves {{l/same\|HEAD}} to point to the branch called "name"
	==Links==		==Links==
	===Reference===		===Reference===
	* [http://git-scm.com/book/en/v2/Git-Branching-Branches-in-a-Nutshell 3.1 Git Branching - Branches in a Nutshell]		* [http://git-scm.com/book/en/v2/Git-Branching-Branches-in-a-Nutshell 3.1 Git Branching - Branches in a Nutshell]