Gitlab - Getting Started - Revision history

Jkinne: /* Windows - Using Putty */

2026-08-30T17:21:56Z

Windows - Using Putty

← Older revision		Revision as of 17:21, 30 August 2026
Line 36:		Line 36:
	<pre>[Environment]::SetEnvironmentVariable("GIT_SSH", "plink.exe", "User")		<pre>[Environment]::SetEnvironmentVariable("GIT_SSH", "plink.exe", "User")
	git config --global core.sshCommand "plink.exe"</pre>		git config --global core.sshCommand "plink.exe"</pre>
	* Open the app PuttyGen (that is installed along with Putty). Click "Load", and load your private key file (id_ed25519 if you used default settings). Then click "Save private key", and save the private key in the ppk format (and store it in your .ssh directory).		* Open the app PuttyGen (that is installed along with Putty). Click "Load", and load your private key file (id_ed25519 if you used default settings); you will need to change the Filename selector to "All Files" rather than "Putty Private Key Files". Then click "Save private key", and save the private key in the ppk format (and store it in your .ssh directory); use the same filename but put ".ppk" at the end.
	* Open the app Pageant (that is also installed along with Putty). This runs in the background, so nothing will appear on the screen. Look in your system tray for a new icon. Click on the Pageant icon in the system tray, right-click on it, and click "Add key". Select the ppk file you just produced.		* Open the app Pageant (that is also installed along with Putty). This runs in the background, so nothing will appear on the screen. Look in your system tray for a new icon. Click on the Pageant icon in the system tray, right-click on it, and click "Add key". Select the ppk file you just produced.
	* Close your terminal windows and open a new one. Try running the git pull command again.		* Close your terminal windows and open a new one. Try running the git pull command again. Note that you may need to delete the "hello-class" directory if it was created by trying to run the git pull previously (even if it fails, it might make the directory).

	=Getting Around=		=Getting Around=

Jkinne: /* Windows - Using Putty */

2026-08-30T17:13:54Z

Windows - Using Putty

← Older revision		Revision as of 17:13, 30 August 2026
Line 36:		Line 36:
	<pre>[Environment]::SetEnvironmentVariable("GIT_SSH", "plink.exe", "User")		<pre>[Environment]::SetEnvironmentVariable("GIT_SSH", "plink.exe", "User")
	git config --global core.sshCommand "plink.exe"</pre>		git config --global core.sshCommand "plink.exe"</pre>
	* Open the app PuttyGen (that is installed along with Putty). Click "Load", and load your private key file (id_ed25519 if you used default settings). Then click "Save private key", and save the private key in the ppk format (~~may as well~~ store it in your .ssh directory).		* Open the app PuttyGen (that is installed along with Putty). Click "Load", and load your private key file (id_ed25519 if you used default settings). Then click "Save private key", and save the private key in the ppk format (and store it in your .ssh directory).
	* Open the app Pageant (that is also installed along with Putty). This runs in the background, so nothing will appear on the screen. Look in your system tray for a new icon. Click on the Pageant icon in the system tray, right-click on it, and click "Add key". Select the ppk file you just produced.		* Open the app Pageant (that is also installed along with Putty). This runs in the background, so nothing will appear on the screen. Look in your system tray for a new icon. Click on the Pageant icon in the system tray, right-click on it, and click "Add key". Select the ppk file you just produced.
	* Close your terminal windows and open a new one. Try running the git pull command again.		* Close your terminal windows and open a new one. Try running the git pull command again.

Jkinne: /* Windows - Using Putty */

2026-08-30T17:13:21Z

Windows - Using Putty

← Older revision		Revision as of 17:13, 30 August 2026
Line 33:		Line 33:
	If you are on Windows and are getting an access error when you tro to run the git clone command, it might work by changing the configuration for git to use a different program for ssh. You can try the following.		If you are on Windows and are getting an access error when you tro to run the git clone command, it might work by changing the configuration for git to use a different program for ssh. You can try the following.
	* Download and install Putty from: https://www.chiark.greenend.org.uk/~sgtatham/putty/latest.html		* Download and install Putty from: https://www.chiark.greenend.org.uk/~sgtatham/putty/latest.html
	* Open your terminal (~~command prompt~~) and run the following commands:		* Open your terminal (PowerShell) and run the following commands:
	<pre>[Environment]::SetEnvironmentVariable("GIT_SSH", "plink.exe", "User")		<pre>[Environment]::SetEnvironmentVariable("GIT_SSH", "plink.exe", "User")
	git config --global core.sshCommand "plink.exe"</pre>		git config --global core.sshCommand "plink.exe"</pre>

Jkinne: /* SSH Keys */

2026-08-30T17:12:49Z

SSH Keys

← Older revision		Revision as of 17:12, 30 August 2026
Line 29:		Line 29:

	You can clone a repository from git.indstate.edu using a command like this: <code>git clone git+ssh://git@git.indstate.edu/ect-437-fall-2026/hello-class.git</code>, but where you would replace the link with whatever repository you are cloning.		You can clone a repository from git.indstate.edu using a command like this: <code>git clone git+ssh://git@git.indstate.edu/ect-437-fall-2026/hello-class.git</code>, but where you would replace the link with whatever repository you are cloning.

			==Windows - Using Putty==
			If you are on Windows and are getting an access error when you tro to run the git clone command, it might work by changing the configuration for git to use a different program for ssh. You can try the following.
			* Download and install Putty from: https://www.chiark.greenend.org.uk/~sgtatham/putty/latest.html
			* Open your terminal (command prompt) and run the following commands:
			<pre>[Environment]::SetEnvironmentVariable("GIT_SSH", "plink.exe", "User")
			git config --global core.sshCommand "plink.exe"</pre>
			* Open the app PuttyGen (that is installed along with Putty). Click "Load", and load your private key file (id_ed25519 if you used default settings). Then click "Save private key", and save the private key in the ppk format (may as well store it in your .ssh directory).
			* Open the app Pageant (that is also installed along with Putty). This runs in the background, so nothing will appear on the screen. Look in your system tray for a new icon. Click on the Pageant icon in the system tray, right-click on it, and click "Add key". Select the ppk file you just produced.
			* Close your terminal windows and open a new one. Try running the git pull command again.

	=Getting Around=		=Getting Around=

Jkinne: /* SSH Keys */

2026-08-23T20:15:46Z

SSH Keys

← Older revision		Revision as of 20:15, 23 August 2026
Line 24:		Line 24:
	You should replace the name git_indstate_id with whatever filename you used for the private key. On Windows, the file should be in your home directory (normally C:\Users\YOUR_USERNAME) and then .ssh/config (so, similar to where it is for Mac and Linux).		You should replace the name git_indstate_id with whatever filename you used for the private key. On Windows, the file should be in your home directory (normally C:\Users\YOUR_USERNAME) and then .ssh/config (so, similar to where it is for Mac and Linux).

	Note - for editing the config file, you should use a plain text editor (Notepad on Windows, TextEdit on Mac, or something nicer; not Word).		Note - for editing the config file, you should use a plain text editor (Notepad on Windows, TextEdit on Mac, or something nicer; not Word).

			Note - you will need to enable the ability to see "hidden" files. On Mac, you press cmd-shift-. to see hidden files in Finder. On Windows, in File Explorer you need to: click the triple dots near the top right, click Options, click View, select "Show files, folders, and drives", and also unselect "Hide extensions for known file types".

	You can clone a repository from git.indstate.edu using a command like this: <code>git clone git+ssh://git@git.indstate.edu/ect-437-fall-2026/hello-class.git</code>, but where you would replace the link with whatever repository you are cloning.		You can clone a repository from git.indstate.edu using a command like this: <code>git clone git+ssh://git@git.indstate.edu/ect-437-fall-2026/hello-class.git</code>, but where you would replace the link with whatever repository you are cloning.

Jkinne: /* SSH Keys */

2026-08-19T17:30:05Z

SSH Keys

← Older revision		Revision as of 17:30, 19 August 2026
Line 23:		Line 23:
	</pre>		</pre>
	You should replace the name git_indstate_id with whatever filename you used for the private key. On Windows, the file should be in your home directory (normally C:\Users\YOUR_USERNAME) and then .ssh/config (so, similar to where it is for Mac and Linux).		You should replace the name git_indstate_id with whatever filename you used for the private key. On Windows, the file should be in your home directory (normally C:\Users\YOUR_USERNAME) and then .ssh/config (so, similar to where it is for Mac and Linux).

			Note - for editing the config file, you should use a plain text editor (Notepad on Windows, TextEdit on Mac, or something nicer; not Word).

	You can clone a repository from git.indstate.edu using a command like this: <code>git clone git+ssh://git@git.indstate.edu/ect-437-fall-2026/hello-class.git</code>, but where you would replace the link with whatever repository you are cloning.		You can clone a repository from git.indstate.edu using a command like this: <code>git clone git+ssh://git@git.indstate.edu/ect-437-fall-2026/hello-class.git</code>, but where you would replace the link with whatever repository you are cloning.

Jkinne: /* Workflow */

2026-08-19T12:31:26Z

Workflow

← Older revision		Revision as of 12:31, 19 August 2026
Line 54:		Line 54:
	git push # sends all committed changes to the remote server		git push # sends all committed changes to the remote server
	</pre>		</pre>
	Note that the push ~~will likely~~ ask for login information to the remote server. ~~Note that if~~ you ~~want there to be a record of a particular version of a file~~, you ~~need to stage/commit the file. It is the commit~~'~~ed versions of files that are stored permanently~~.		Note that the push may ask for login information to the remote server. If you have an ssh key configured for the project (see section above), then you won't be asked for login information.

	'''Pull''' - To pull/download updates that have happened (by others), you use <code>git pull</code>.		'''Pull''' - To pull/download updates that have happened (by others), you use <code>git pull</code>.

Jkinne: /* SSH Keys */

2026-08-19T12:29:51Z

SSH Keys

← Older revision		Revision as of 12:29, 19 August 2026
Line 22:		Line 22:
	IdentityFile ~/.ssh/git_indstate_id		IdentityFile ~/.ssh/git_indstate_id
	</pre>		</pre>
	You should replace the name git_indstate_id with whatever filename you used for the private key.		You should replace the name git_indstate_id with whatever filename you used for the private key. On Windows, the file should be in your home directory (normally C:\Users\YOUR_USERNAME) and then .ssh/config (so, similar to where it is for Mac and Linux).

	You can clone a repository from git.indstate.edu using a command like this: <code>git clone git+ssh://git@git.indstate.edu/ect-437-fall-2026/hello-class.git</code>, but where you would replace the link with whatever repository you are cloning.		You can clone a repository from git.indstate.edu using a command like this: <code>git clone git+ssh://git@git.indstate.edu/ect-437-fall-2026/hello-class.git</code>, but where you would replace the link with whatever repository you are cloning.

Jkinne: /* SSH Keys */

2026-08-06T16:40:13Z

SSH Keys

@@ Line 15: / Line 15: @@
 =SSH Keys=
 You will normally want to have SSH keys setup so that you can interact with the git server without having to enter a username and password. Instructions are here: https://docs.gitlab.com/user/ssh/
 =Getting Around=

Jkinne: /* Account Setup */

2026-08-06T14:58:04Z

Account Setup

← Older revision		Revision as of 14:58, 6 August 2026
Line 12:		Line 12:

	'''On git.indstate.edu''' - ISU's local installation of gitlab is at https://git.indstate.edu/. For this system you use your ISU portal id and password. You do not need to create an account. The first time you login into the system, it initializes an account for you. CS courses and ISU CS projects in general tend to use ISU's local installation because we can tie access based on course rosters, etc.		'''On git.indstate.edu''' - ISU's local installation of gitlab is at https://git.indstate.edu/. For this system you use your ISU portal id and password. You do not need to create an account. The first time you login into the system, it initializes an account for you. CS courses and ISU CS projects in general tend to use ISU's local installation because we can tie access based on course rosters, etc.

			=SSH Keys=
			You will normally want to have SSH keys setup so that you can interact with the git server without having to enter a username and password. Instructions are here: https://docs.gitlab.com/user/ssh/

	=Getting Around=		=Getting Around=