Git - Revision history

Prabuanand: moved content from Aports tree page

2025-10-06T05:15:04Z

moved content from Aports tree page

← Older revision		Revision as of 05:15, 6 October 2025
Line 37:		Line 37:

	=== Cloning your forked repository ===		=== Cloning your forked repository ===

			By cloning the aports from the server, you are fetching the APKBUILD files along with other build-related files for each Alpine package from the [[Aports tree\|aports tree]] to your local build environment. You can clone your [[#Forking a repository\|forked]] repository, by replacing $USER with the nickname of your Gitlab account and $REPO in the git command: {{Cmd\|$ git clone <nowiki>git@gitlab.alpinelinux.org:$USER/$REPO.git</nowiki>}}

	You can clone your [[#Forking a repository\|forked]] repository, by replacing $USER with the nickname of your Gitlab account and $REPO in the git command: {{Cmd\|$ git clone <nowiki>git@gitlab.alpinelinux.org:$USER/$REPO.git</nowiki>}}		Before you clone the '''aports''' repository, switch to the directory you want to have the {{Path\|aports/}} directory. To clone aports into {{Path\|~/src/aports}} or {{Path\|~/aports}}, issue the commands {{ic\|$ cd ~/src/}} or {{ic\|$ cd ~/}} respectively.

	Before you clone the '''aports''' repository, switch to the directory you want to have the {{Path\|aports/}} directory. To clone aports into {{Path\|~/src/aports}}, issue the ~~command:~~{{~~Cmd~~\|$ cd ~/src/}}

	To clone your [[#Forking a repository\|forked]] '''aports''' repository with only the last 3 revisions, replace $USER and issue the command: {{Cmd\|$ git clone <nowiki>git@gitlab.alpinelinux.org:$USER/aports.git</nowiki> --depth 3}}		To clone your [[#Forking a repository\|forked]] '''aports''' repository with only the last 3 revisions, replace $USER and issue the command: {{Cmd\|$ git clone <nowiki>git@gitlab.alpinelinux.org:$USER/aports.git</nowiki> --depth 3}}

Prabuanand: fixed url typo

2025-10-05T19:15:19Z

fixed url typo

← Older revision		Revision as of 19:15, 5 October 2025
Line 23:		Line 23:
	Follow the below instructions to setup an account in the [https://gitlab.alpinelinux.org Alpine Linux' Gitlab instance].		Follow the below instructions to setup an account in the [https://gitlab.alpinelinux.org Alpine Linux' Gitlab instance].

	* Create an account ~~for it~~ https://gitlab.alpinelinux.org/users/sign_in.		* Create an account at https://gitlab.alpinelinux.org/users/sign_in.
	* It's recommended to set a SSH key now, refer to the [https://docs.gitlab.com/ee/ssh/ Gitlab docs] for how to do that.		* It's recommended to set a SSH key now, refer to the [https://docs.gitlab.com/user/ssh/ Gitlab docs] for how to do that.

	=== Forking a repository ===		=== Forking a repository ===

Prabuanand: fixed the changed url

2025-10-05T17:49:29Z

fixed the changed url

← Older revision		Revision as of 17:49, 5 October 2025
Line 28:		Line 28:
	=== Forking a repository ===		=== Forking a repository ===

	To [[Creating an Alpine package\|create an Alpine package]] or [[Creating patches\|submit a patch]] without write access to the Alpine repository, you need to fork the desired repository. [[#~~Creating a~~ gitlab account\|~~Create a~~ gitlab account]], if not already done.		To [[Creating an Alpine package\|create an Alpine package]] or [[Creating patches\|submit a patch]] without write access to the Alpine repository, you need to fork the desired repository. [[#Setup gitlab account\|Setup gitlab account]], if not already done.

	For packages, create a fork for '''aports''' at https://gitlab.alpinelinux.org/alpine/aports. Refer [https://docs.gitlab.com/ee/user/project/repository/forking_workflow.html#creating-a-fork Gitlab docs] if you're having problems with that.		For packages, create a fork for '''aports''' at https://gitlab.alpinelinux.org/alpine/aports. Refer [https://docs.gitlab.com/ee/user/project/repository/forking_workflow.html#creating-a-fork Gitlab docs] if you're having problems with that.

Prabuanand: changed format

2025-10-05T17:47:39Z

changed format

← Older revision		Revision as of 17:47, 5 October 2025
Line 23:		Line 23:
	Follow the below instructions to setup an account in the [https://gitlab.alpinelinux.org Alpine Linux' Gitlab instance].		Follow the below instructions to setup an account in the [https://gitlab.alpinelinux.org Alpine Linux' Gitlab instance].

	* Create an account for it [https://gitlab.alpinelinux.org/users/sign_in ~~here]~~.		* Create an account for it https://gitlab.alpinelinux.org/users/sign_in.
	* It's recommended to set a SSH key now, refer to the [https://docs.gitlab.com/ee/ssh/ Gitlab docs] for how to do that.		* It's recommended to set a SSH key now, refer to the [https://docs.gitlab.com/ee/ssh/ Gitlab docs] for how to do that.

Prabuanand: moved content from Creating patches page

2025-10-05T17:45:37Z

moved content from Creating patches page

← Older revision		Revision as of 17:45, 5 October 2025
Line 19:		Line 19:
	{{Tip\|If you want to use git with proxy server:{{Cmd\|git config --global http.proxy <nowiki>http://proxy_ip:proxy_port</nowiki>}}}}		{{Tip\|If you want to use git with proxy server:{{Cmd\|git config --global http.proxy <nowiki>http://proxy_ip:proxy_port</nowiki>}}}}

	=== ~~Creating a~~ gitlab account ===		=== Setup gitlab account ===

	~~Visit~~ [https://gitlab.alpinelinux.org Alpine gitlab] to ~~create~~ a gitlab ~~account~~.		Follow the below instructions to setup an account in the [https://gitlab.alpinelinux.org Alpine Linux' Gitlab instance].

			* Create an account for it [https://gitlab.alpinelinux.org/users/sign_in here].
			* It's recommended to set a SSH key now, refer to the [https://docs.gitlab.com/ee/ssh/ Gitlab docs] for how to do that.

	=== Forking a repository ===		=== Forking a repository ===

Prabuanand: added necessary command

2025-10-05T17:25:44Z

added necessary command

← Older revision		Revision as of 17:25, 5 October 2025
Line 37:		Line 37:
	You can clone your [[#Forking a repository\|forked]] repository, by replacing $USER with the nickname of your Gitlab account and $REPO in the git command: {{Cmd\|$ git clone <nowiki>git@gitlab.alpinelinux.org:$USER/$REPO.git</nowiki>}}		You can clone your [[#Forking a repository\|forked]] repository, by replacing $USER with the nickname of your Gitlab account and $REPO in the git command: {{Cmd\|$ git clone <nowiki>git@gitlab.alpinelinux.org:$USER/$REPO.git</nowiki>}}

	Before you clone the '''aports''' repository, switch to the directory you want to have the {{Path\|aports/}} directory. To clone your [[#Forking a repository\|forked]] '''aports''' repository with only the last 3 revisions, replace $USER and issue the command: {{Cmd\|$ git clone <nowiki>git@gitlab.alpinelinux.org:$USER/aports.git</nowiki> --depth 3}}		Before you clone the '''aports''' repository, switch to the directory you want to have the {{Path\|aports/}} directory. To clone aports into {{Path\|~/src/aports}}, issue the command:{{Cmd\|$ cd ~/src/}}

			To clone your [[#Forking a repository\|forked]] '''aports''' repository with only the last 3 revisions, replace $USER and issue the command: {{Cmd\|$ git clone <nowiki>git@gitlab.alpinelinux.org:$USER/aports.git</nowiki> --depth 3}}

	To see the full log of the trunk, use the command below: {{Cmd\|git log}}		To see the full log of the trunk, use the command below: {{Cmd\|git log}}

Prabuanand: moved content from Creating patches

2025-10-05T17:06:10Z

moved content from Creating patches

← Older revision		Revision as of 17:06, 5 October 2025
Line 27:		Line 27:
	To [[Creating an Alpine package\|create an Alpine package]] or [[Creating patches\|submit a patch]] without write access to the Alpine repository, you need to fork the desired repository. [[#Creating a gitlab account\|Create a gitlab account]], if not already done.		To [[Creating an Alpine package\|create an Alpine package]] or [[Creating patches\|submit a patch]] without write access to the Alpine repository, you need to fork the desired repository. [[#Creating a gitlab account\|Create a gitlab account]], if not already done.

	~~Create~~ a fork for '''aports''' at https://gitlab.alpinelinux.org/alpine/aports. Refer [https://docs.gitlab.com/ee/user/project/repository/forking_workflow.html#creating-a-fork Gitlab docs] if you're having problems with that.		For packages, create a fork for '''aports''' at https://gitlab.alpinelinux.org/alpine/aports. Refer [https://docs.gitlab.com/ee/user/project/repository/forking_workflow.html#creating-a-fork Gitlab docs] if you're having problems with that.

			If you want to contribute to other repositories belonging to Alpine Linux, they live in the [https://gitlab.alpinelinux.org/alpine Alpine organisation] and you may want to fork them as above.

	Once created, the fork resides on the Gitlab server, until you [[#Cloning your forked repository\|clone your fork]].		Once created, the fork resides on the Gitlab server, until you [[#Cloning your forked repository\|clone your fork]].

Sertonix: fix broken link

2025-10-05T13:02:52Z

fix broken link

← Older revision		Revision as of 13:02, 5 October 2025
Line 9:		Line 9:
	* with write access.		* with write access.

	Most contributors to Alpine linux will be working [[#~~Submitting work without write access~~\|~~without write access~~]]. Only [https://docs.alpinelinux.org/governance/0.1b/Teams/developers.html Alpine Developers] have write access.		Most contributors to Alpine linux will be working [[#Forking a repository\|with a forked repository]]. Only [https://docs.alpinelinux.org/governance/0.1b/Teams/developers.html Alpine Developers] have write access.

	Follow this [[Creating_an_Alpine_package#Overview\|overview]] to [[Creating an Alpine package\|create a package]] or [[Creating patches\|submit a patch]] even without write access.		Follow this [[Creating_an_Alpine_package#Overview\|overview]] to [[Creating an Alpine package\|create a package]] or [[Creating patches\|submit a patch]] even without write access.

Sertonix: Not having write access is the standard for almost all contributors, not only new ones

2025-10-05T12:55:44Z

Not having write access is the standard for almost all contributors, not only new ones

← Older revision		Revision as of 12:55, 5 October 2025
Line 9:		Line 9:
	* with write access.		* with write access.

	~~New~~ contributors to Alpine linux will be working [[#Submitting work without write access\|without write access]]. Only [https://docs.alpinelinux.org/governance/0.1b/Teams/developers.html Alpine Developers] have write access.		Most contributors to Alpine linux will be working [[#Submitting work without write access\|without write access]]. Only [https://docs.alpinelinux.org/governance/0.1b/Teams/developers.html Alpine Developers] have write access.

	Follow this [[Creating_an_Alpine_package#Overview\|overview]] to [[Creating an Alpine package\|create a package]] or [[Creating patches\|submit a patch]] even without write access.		Follow this [[Creating_an_Alpine_package#Overview\|overview]] to [[Creating an Alpine package\|create a package]] or [[Creating patches\|submit a patch]] even without write access.

Prabuanand: minor rewording to make understanding easier

2025-10-03T11:27:13Z

minor rewording to make understanding easier

← Older revision		Revision as of 11:27, 3 October 2025
Line 1:		Line 1:
	This document describes how to use [https://git-scm.com git] for Alpine Linux development ~~and related projects~~. If you just want to browse all the available Alpine git repositories, [https://git.alpinelinux.org git.alpinelinux.org] shows them all.		This document describes how to use [https://git-scm.com git] for Alpine Linux development. If you just want to browse all the available Alpine git repositories, [https://git.alpinelinux.org git.alpinelinux.org] shows them all.

	If you are new to git and need quick reference, check [[#Git Basics\|Git Basics]]. For more info, refer [[#Further reading\|further reading]] section.		If you are new to git and need quick reference, check [[#Git Basics\|Git Basics]]. For more info, refer [[#Further reading\|further reading]] section.

	~~{{:Development_using_git:Configuration}}~~
	~~{{Tip\| If you want to use git with colored output use:~~
	~~{{Cmd\|git config --global color.ui true~~
	~~git config --global core.pager more}}~~
	}}

	~~{{Tip\|If you want to use git with proxy server:{{Cmd\|git config --global http.proxy <nowiki>http://proxy_ip:proxy_port</nowiki>}}}}~~

	== General git workflow ==		== General git workflow ==
Line 17:		Line 9:
	* with write access.		* with write access.

	~~Most instructions on this page is meant for new~~ contributors ~~who~~ will be working [[#Submitting work without write access\|without write access]]. Only [https://docs.alpinelinux.org/governance/0.1b/Teams/developers.html Alpine Developers] have write access. ~~You can still~~ [[Creating an Alpine package\|create ~~an Alpine~~ package]] or [[Creating patches\|submit a patch]] without write access to ~~the Alpine repository as per this [[Creating_an_Alpine_package#Overview~~\|~~overview]]~~.		New contributors to Alpine linux will be working [[#Submitting work without write access\|without write access]]. Only [https://docs.alpinelinux.org/governance/0.1b/Teams/developers.html Alpine Developers] have write access.

			Follow this [[Creating_an_Alpine_package#Overview\|overview]] to [[Creating an Alpine package\|create a package]] or [[Creating patches\|submit a patch]] even without write access.

			=== Configure your global git config ===
			{{:Include:Git configuration}}
			If you want to use git with colored output use:{{Cmd\|git config --global color.ui true
			git config --global core.pager more}}
			{{Tip\|If you want to use git with proxy server:{{Cmd\|git config --global http.proxy <nowiki>http://proxy_ip:proxy_port</nowiki>}}}}

	=== Creating a gitlab account ===		=== Creating a gitlab account ===
Line 29:		Line 29:
	Create a fork for '''aports''' at https://gitlab.alpinelinux.org/alpine/aports. Refer [https://docs.gitlab.com/ee/user/project/repository/forking_workflow.html#creating-a-fork Gitlab docs] if you're having problems with that.		Create a fork for '''aports''' at https://gitlab.alpinelinux.org/alpine/aports. Refer [https://docs.gitlab.com/ee/user/project/repository/forking_workflow.html#creating-a-fork Gitlab docs] if you're having problems with that.

	~~{{Note\|Note that~~ the fork resides on the Gitlab server, until you [[#Cloning a repository ~~via Git~~\|clone your fork]].}}		Once created, the fork resides on the Gitlab server, until you [[#Cloning your forked repository\|clone your fork]].

	=== Cloning your forked repository ===		=== Cloning your forked repository ===

← Older revision		Revision as of 17:25, 5 October 2025
Line 37:		Line 37:
	You can clone your [[#Forking a repository\|forked]] repository, by replacing $USER with the nickname of your Gitlab account and $REPO in the git command: {{Cmd\|$ git clone <nowiki>git@gitlab.alpinelinux.org:$USER/$REPO.git</nowiki>}}		You can clone your [[#Forking a repository\|forked]] repository, by replacing $USER with the nickname of your Gitlab account and $REPO in the git command: {{Cmd\|$ git clone <nowiki>git@gitlab.alpinelinux.org:$USER/$REPO.git</nowiki>}}

	Before you clone the '''aports''' repository, switch to the directory you want to have the {{Path\|aports/}} directory. To clone your [[#Forking a repository\|forked]] '''aports''' repository with only the last 3 revisions, replace $USER and issue the command: {{Cmd\|$ git clone <nowiki>git@gitlab.alpinelinux.org:$USER/aports.git</nowiki> --depth 3}}		Before you clone the '''aports''' repository, switch to the directory you want to have the {{Path\|aports/}} directory. To clone aports into {{Path\|~/src/aports}}, issue the command:{{Cmd\|$ cd ~/src/}}

			To clone your [[#Forking a repository\|forked]] '''aports''' repository with only the last 3 revisions, replace $USER and issue the command: {{Cmd\|$ git clone <nowiki>git@gitlab.alpinelinux.org:$USER/aports.git</nowiki> --depth 3}}

	To see the full log of the trunk, use the command below: {{Cmd\|git log}}		To see the full log of the trunk, use the command below: {{Cmd\|git log}}