Git/notes - Revision history

Woozle: /* Answers */

2022-07-31T16:10:07Z

Answers

← Older revision		Revision as of 16:10, 31 July 2022
Line 26:		Line 26:

	==Answers==		==Answers==
			* '''Q:''' Where are git settings stored?
			** '''A:''' User settings are stored in <code>~/.gitconfig</code>; not sure where global settings are stored.
	* '''Q:''' How do I store my username & password so I don't have to enter it each time I "git push origin"?		* '''Q:''' How do I store my username & password so I don't have to enter it each time I "git push origin"?
	** '''A:''' <syntaxhighlight lang=bash>git config --global credential.helper 'cache --timeout=10000000'</syntaxhighlight>		** '''A:''' <syntaxhighlight lang=bash inline>git config --global credential.helper 'cache --timeout=10000000'</syntaxhighlight>
	*** This doesn't store it permanently, but will "cache" it for --timeout seconds.		*** This doesn't store it permanently, but will "cache" it for --timeout seconds.
	* When <code>git pull github</code> returns this:		* When <code>git pull github</code> returns this:

Woozle at 16:06, 31 July 2022

2022-07-31T16:06:48Z

← Older revision		Revision as of 16:06, 31 July 2022
Line 1:		Line 1:
	==How To==		==How To==
			===status in bash===
	To make {{l/linux/cmd\|bash}} git-aware, add this line to <code>~/.bashrc</code> (not sure if it matters where in the file):		To make {{l/linux/cmd\|bash}} git-aware, add this line to <code>~/.bashrc</code> (not sure if it matters where in the file):
	<syntaxhighlight lang=bash>		<syntaxhighlight lang=bash>
Line 8:		Line 9:
	</syntaxhighlight>		</syntaxhighlight>
	This causes bash to show the current branch as part of the command prompt. You will need to [https://stackoverflow.com/a/2518150 reload bash's config] for it to take effect.		This causes bash to show the current branch as part of the command prompt. You will need to [https://stackoverflow.com/a/2518150 reload bash's config] for it to take effect.

			===project renaming===
			To rename a project (including the folder-slug):
			* In your origin repository manager (e.g. GitLab), clone the project into a new one (with the folder-slug you want).
			* Clone the project from there to your local workspace.
			* Modify any URLs in <code>{{arg\|project}}/.git/config</code> that point to the old folder.
			* Stage, commit, and push back to the origin.
	==Questions==		==Questions==
	''questions that have not yet been answered''		''questions that have not yet been answered''

Woozle at 15:12, 31 July 2022

2022-07-31T15:12:18Z

← Older revision		Revision as of 15:12, 31 July 2022
Line 1:		Line 1:
	==How To==		==How To==
	To make {{l/linux/cmd\|bash}} git-aware, add this line to <code>~/.bashrc</code> (not sure if it matters where in the file):		To make {{l/linux/cmd\|bash}} git-aware, add this line to <code>~/.bashrc</code> (not sure if it matters where in the file):
	<~~source~~ lang=bash>		<syntaxhighlight lang=bash>
	parse_git_branch() {		parse_git_branch() {
	git branch 2> /dev/null \| sed -e '/^[^]/d' -e 's/ $.*$/ (\1)/'		git branch 2> /dev/null \| sed -e '/^[^]/d' -e 's/ $.*$/ (\1)/'
	}		}
	export PS1="\u@\h \[\033[01;32m\]\w\[\033[33m\]\$(parse_git_branch)\[\033[00m\] $ "		export PS1="\u@\h \[\033[01;32m\]\w\[\033[33m\]\$(parse_git_branch)\[\033[00m\] $ "
	</~~source~~>		</syntaxhighlight>
	This causes bash to show the current branch as part of the command prompt. You will need to [https://stackoverflow.com/a/2518150 reload bash's config] for it to take effect.		This causes bash to show the current branch as part of the command prompt. You will need to [https://stackoverflow.com/a/2518150 reload bash's config] for it to take effect.
	==Questions==		==Questions==

Woozle at 18:23, 1 September 2019

2019-09-01T18:23:16Z

← Older revision		Revision as of 18:23, 1 September 2019
Line 7:		Line 7:
	export PS1="\u@\h \[\033[01;32m\]\w\[\033[33m\]\$(parse_git_branch)\[\033[00m\] $ "		export PS1="\u@\h \[\033[01;32m\]\w\[\033[33m\]\$(parse_git_branch)\[\033[00m\] $ "
	</source>		</source>
	This causes bash to show the current branch as part of the command prompt.		This causes bash to show the current branch as part of the command prompt. You will need to [https://stackoverflow.com/a/2518150 reload bash's config] for it to take effect.
	==Questions==		==Questions==
	''questions that have not yet been answered''		''questions that have not yet been answered''

Woozle: oops

2019-09-01T18:19:23Z

oops

← Older revision		Revision as of 18:19, 1 September 2019
Line 1:		Line 1:
	==How To==		==How To==
	To make {{l/linux/cmd\|bash}} git-aware, add this line to <code>~/.~~bash~~</code> (not sure if it matters where in the file):		To make {{l/linux/cmd\|bash}} git-aware, add this line to <code>~/.bashrc</code> (not sure if it matters where in the file):
	<source lang=bash>		<source lang=bash>
	parse_git_branch() {		parse_git_branch() {

Woozle at 18:13, 1 September 2019

2019-09-01T18:13:47Z

← Older revision		Revision as of 18:13, 1 September 2019
Line 7:		Line 7:
	export PS1="\u@\h \[\033[01;32m\]\w\[\033[33m\]\$(parse_git_branch)\[\033[00m\] $ "		export PS1="\u@\h \[\033[01;32m\]\w\[\033[33m\]\$(parse_git_branch)\[\033[00m\] $ "
	</source>		</source>
			This causes bash to show the current branch as part of the command prompt.
	==Questions==		==Questions==
	''questions that have not yet been answered''		''questions that have not yet been answered''

Woozle at 18:12, 1 September 2019

2019-09-01T18:12:33Z

← Older revision		Revision as of 18:12, 1 September 2019
Line 1:		Line 1:
			==How To==
			To make {{l/linux/cmd\|bash}} git-aware, add this line to <code>~/.bash</code> (not sure if it matters where in the file):
			<source lang=bash>
			parse_git_branch() {
			git branch 2> /dev/null \| sed -e '/^[^]/d' -e 's/ $.*$/ (\1)/'
			}
			export PS1="\u@\h \[\033[01;32m\]\w\[\033[33m\]\$(parse_git_branch)\[\033[00m\] $ "
			</source>
	==Questions==		==Questions==
	''questions that have not yet been answered''		''questions that have not yet been answered''

Woozle at 23:07, 17 December 2017

2017-12-17T23:07:24Z

← Older revision		Revision as of 23:07, 17 December 2017
Line 9:		Line 9:

	==Answers==		==Answers==
			* '''Q:''' How do I store my username & password so I don't have to enter it each time I "git push origin"?
			** '''A:''' <syntaxhighlight lang=bash>git config --global credential.helper 'cache --timeout=10000000'</syntaxhighlight>
			*** This doesn't store it permanently, but will "cache" it for --timeout seconds.
	* When <code>git pull github</code> returns this:		* When <code>git pull github</code> returns this:
	You asked to pull from the remote 'github', but did not specify		You asked to pull from the remote 'github', but did not specify

Woozle: /* Questions */ Q! I should have known you were supposed to be behind this sentence...

2015-03-09T21:26:17Z

Questions: Q! I should have known you were supposed to be behind this sentence...

← Older revision		Revision as of 21:26, 9 March 2015
Line 6:		Line 6:
	** '''Q:''' If the four conditions apply to changes (not files), then does it make sense to talk about "staging files"?		** '''Q:''' If the four conditions apply to changes (not files), then does it make sense to talk about "staging files"?
	** '''Q:''' How do you get a list of all the files that have been staged, whether or not they are "modified"?		** '''Q:''' How do you get a list of all the files that have been staged, whether or not they are "modified"?
	* Is there any way to set things up so you don't have to keep entering username and password when pushing to a password-protected remote repository (such as GitHub)?		* '''Q:''' Is there any way to set things up so you don't have to keep entering username and password when pushing to a password-protected remote repository (such as GitHub)?

	==Answers==		==Answers==
	* When <code>git pull github</code> returns this:		* When <code>git pull github</code> returns this:

Woozle: another question

2015-03-09T20:50:12Z

another question

← Older revision		Revision as of 20:50, 9 March 2015
Line 6:		Line 6:
	** '''Q:''' If the four conditions apply to changes (not files), then does it make sense to talk about "staging files"?		** '''Q:''' If the four conditions apply to changes (not files), then does it make sense to talk about "staging files"?
	** '''Q:''' How do you get a list of all the files that have been staged, whether or not they are "modified"?		** '''Q:''' How do you get a list of all the files that have been staged, whether or not they are "modified"?
			* Is there any way to set things up so you don't have to keep entering username and password when pushing to a password-protected remote repository (such as GitHub)?
	==Answers==		==Answers==
	* When <code>git pull github</code> returns this:		* When <code>git pull github</code> returns this: