Setting up git - История изменений

imported>Coconutwarrior97: /* Initial Setup */ Fixed typo, congradultions to congratulations.

2023-09-12T23:35:48Z

Initial Setup: Fixed typo, congradultions to congratulations.

← Предыдущая версия		Версия от 23:35, 12 сентября 2023
Строка 22:		Строка 22:

	'''Step 6:'''		'''Step 6:'''
	Next, run '''git init.''' This initializes your workspace. Now your workspace exists, ~~congraduations~~!		Next, run '''git init.''' This initializes your workspace. Now your workspace exists, congratulations!

	'''Step 7:'''		'''Step 7:'''

imported>Arcanemusic: I am bad at numbers

2022-11-17T03:19:00Z

I am bad at numbers

← Предыдущая версия		Версия от 03:19, 17 ноября 2022
Строка 27:		Строка 27:
	Now, run '''git remote add origin <''yourforkurlfromstep3.''>''' This is going to create a source for you to pull your code from called '''''origin'''''.		Now, run '''git remote add origin <''yourforkurlfromstep3.''>''' This is going to create a source for you to pull your code from called '''''origin'''''.

	'''Step 6:'''		'''Step 8:'''
	Next, also in command line, enter: '''''cd tgstation.''''' It doesn't have to be tgstation, but whatever your file holding the tgstation repo code should be what you run, even '''cd dinglesparce''' if your file was named dinglesparce, you wildcard you.		Next, also in command line, enter: '''''cd tgstation.''''' It doesn't have to be tgstation, but whatever your file holding the tgstation repo code should be what you run, even '''cd dinglesparce''' if your file was named dinglesparce, you wildcard you.

	'''Step 7:'''		'''Step 9:'''
	Then, finally, enter: '''''git remote add upstream https://github.com/tgstation/tgstation.git'''''. This will make sure that the tgstation main repo is assigned to a remote branch, similar to your origin branch, called '''''upstream'''''.		Then, finally, enter: '''''git remote add upstream https://github.com/tgstation/tgstation.git'''''. This will make sure that the tgstation main repo is assigned to a remote branch, similar to your origin branch, called '''''upstream'''''.

imported>Arcanemusic: I fixed the guide. It only took 2+ years.

2022-11-17T03:17:38Z

I fixed the guide. It only took 2+ years.

← Предыдущая версия		Версия от 03:17, 17 ноября 2022
Строка 1:		Строка 1:
	This guide (Updated 8/13/~~2020~~) will set up your local version of the code, and your github fork using GIT/GITBASH.		This guide (Updated '''11/16/2022''') will set up your local version of the code, and your github fork using GIT/GITBASH.

	= Git Bash =		= Git Bash =
Строка 22:		Строка 22:

	'''Step 6:'''		'''Step 6:'''
	Next, also in command line, enter: '''''cd tgstation'''''		Next, run '''git init.''' This initializes your workspace. Now your workspace exists, congraduations!
	Then, finally, enter: '''''git remote add upstream https://github.com/tgstation/tgstation.git'''''
			'''Step 7:'''
			Now, run '''git remote add origin <''yourforkurlfromstep3.''>''' This is going to create a source for you to pull your code from called '''''origin'''''.

			'''Step 6:'''
			Next, also in command line, enter: '''''cd tgstation.''''' It doesn't have to be tgstation, but whatever your file holding the tgstation repo code should be what you run, even '''cd dinglesparce''' if your file was named dinglesparce, you wildcard you.

			'''Step 7:'''
			Then, finally, enter: '''''git remote add upstream https://github.com/tgstation/tgstation.git'''''. This will make sure that the tgstation main repo is assigned to a remote branch, similar to your origin branch, called '''''upstream'''''.

	This should cover everything you need to get started, but now lets talk about actually USING git for something practical.		This should cover everything you need to get started, but now lets talk about actually USING git for something practical.

imported>TheFinalPotato: hhhhh

2022-03-09T10:45:20Z

hhhhh

← Предыдущая версия		Версия от 10:45, 9 марта 2022
Строка 70:		Строка 70:
	Now that your changes are staged, you need to commit them. Run '''''git commit -m "<words>"'''''. Every commit that's pushed to a PR is labeled in order to work with that excellent version control mentioned earlier, so if you needed to revert your code back to a old commit, it's possible to do so, and well indexed. This would create a commit with the changes to freshmemes.dm, labeled <words>, but please god give your commits a slightly descriptive name, at least.		Now that your changes are staged, you need to commit them. Run '''''git commit -m "<words>"'''''. Every commit that's pushed to a PR is labeled in order to work with that excellent version control mentioned earlier, so if you needed to revert your code back to a old commit, it's possible to do so, and well indexed. This would create a commit with the changes to freshmemes.dm, labeled <words>, but please god give your commits a slightly descriptive name, at least.

	Now we're nearly done, all you need to do now is run '''''git push origin'''''. If it's your first time pushing this code to github on that branch, you'll be asked to instead run '''''git push origin --set-upstream ~~argument~~'''''. This is normal and expected. Once that's done, on your fork on the github website, as well as on your local code, your same branch will be hosted. This will enable you to PR your code to the main repo without needing to devolve into a disgusting web-editor.		Now we're nearly done, all you need to do now is run '''''git push origin'''''. If it's your first time pushing this code to github on that branch, you'll be asked to instead run '''''git push origin --set-upstream <branch'''''>, where <branch> is your current active branch. This is normal and expected. Once that's done, on your fork on the github website, as well as on your local code, your same branch will be hosted. This will enable you to PR your code to the main repo without needing to devolve into a disgusting web-editor.

	= Other Guides =		= Other Guides =

imported>Bawhoppennn: Coding

2022-02-17T03:25:07Z

Coding

← Предыдущая версия		Версия от 03:25, 17 февраля 2022
Строка 82:		Строка 82:

	{{Contribution guides}}		{{Contribution guides}}
			[[Category:Coding]]

imported>SpaceManiac: Fix weird line break in author's note

2020-12-25T07:47:47Z

Fix weird line break in author's note

← Предыдущая версия		Версия от 07:47, 25 декабря 2020
Строка 31:		Строка 31:
	\|Image=Warningsign.png		\|Image=Warningsign.png
	\|Note=		\|Note=
	Now that your git is set up, you may want to also download [https://code.visualstudio.com/ Visual Studio Code], as there are plugins and add-ons that make working with byond code and the rest of the codebase		Now that your git is set up, you may want to also download [https://code.visualstudio.com/ Visual Studio Code], as there are plugins and add-ons that make working with byond code and the rest of the codebase significantly easier, but you can avoid that for now if you just want to get familiar with gitbash and the codebase (But #coderbus will ask you to download it at some point anyway).

	significantly easier, but you can avoid that for now if you just want to get familiar with gitbash and the codebase (But #coderbus will ask you to download it at some point anyway).
	\|Color=#00F		\|Color=#00F
	}}		}}

imported>SpaceManiac: Remove extra word in remote-add-upstream command

2020-12-25T05:50:29Z

Remove extra word in remote-add-upstream command

← Предыдущая версия		Версия от 05:50, 25 декабря 2020
Строка 23:		Строка 23:
	'''Step 6:'''		'''Step 6:'''
	Next, also in command line, enter: '''''cd tgstation'''''		Next, also in command line, enter: '''''cd tgstation'''''
	Then, finally, enter: '''''git remote add upstream ~~git~~ https://github.com/tgstation/tgstation.git'''''		Then, finally, enter: '''''git remote add upstream https://github.com/tgstation/tgstation.git'''''

	This should cover everything you need to get started, but now lets talk about actually USING git for something practical.		This should cover everything you need to get started, but now lets talk about actually USING git for something practical.

imported>SpaceManiac: Move TortoiseGit to its own page, add Goonstation link

2020-12-25T05:40:55Z

Move TortoiseGit to its own page, add Goonstation link

Внесённые изменения

imported>SpaceManiac: Remove "Game Resources" category

2020-12-04T03:47:35Z

Remove "Game Resources" category

← Предыдущая версия		Версия от 03:47, 4 декабря 2020
Строка 244:		Строка 244:
	</div>		</div>

	~~----~~

	{{Contribution guides}}		{{Contribution guides}}
	~~[[Category:Game Resources]] [[Category:Guides]]~~

imported>SpaceManiac: Use GitHub link for Coding Standards

2020-11-30T08:10:47Z

Use GitHub link for Coding Standards

← Предыдущая версия		Версия от 08:10, 30 ноября 2020
Строка 192:		Строка 192:
	* A commit is confirmed change of the files in your repo, it's how you make changes permanently to the files in your repo, so try not to commit without making sure it works (though subsequent commits can fix it).		* A commit is confirmed change of the files in your repo, it's how you make changes permanently to the files in your repo, so try not to commit without making sure it works (though subsequent commits can fix it).
	* As said before, you should use different branches to separate your commits/changes. Don't commit to master. It should be clean, so you can fall back on it if needed.		* As said before, you should use different branches to separate your commits/changes. Don't commit to master. It should be clean, so you can fall back on it if needed.
	* To make your commits, you need to edit the files using BYOND's inbuilt editing tools. Make sure to [~~[Coding Standards\|~~follow coding standards]] when making your changes! When you're finished, right click the folder you're working with and choose '''Git Commit -> "[Your Branch Name]"''' (Example: Git Commit -> "My_First_Branch")		* To make your commits, you need to edit the files using BYOND's inbuilt editing tools. Make sure to [https://github.com/tgstation/tgstation/blob/master/.github/CONTRIBUTING.md follow coding standards] when making your changes! When you're finished, right click the folder you're working with and choose '''Git Commit -> "[Your Branch Name]"''' (Example: Git Commit -> "My_First_Branch")
	* You can then select only the files you want to be committed by ticking or unticking them. You should also write a detailed commit summary, detailing what happened in that commit.		* You can then select only the files you want to be committed by ticking or unticking them. You should also write a detailed commit summary, detailing what happened in that commit.
	* Click '''Ok''' and the commit will be committed to your local repo!		* Click '''Ok''' and the commit will be committed to your local repo!