GitLab Developer FAQ - Revision history

Mri083: /* My external user account on GitLab does not give me a namespace for forking */

2022-01-20T15:03:11Z

My external user account on GitLab does not give me a namespace for forking

← Older revision		Revision as of 15:03, 20 January 2022
Line 136:		Line 136:

	=== My external user account on GitLab does not give me a namespace for forking ===		=== My external user account on GitLab does not give me a namespace for forking ===
	This is a limitation of GitLab~~, the~~ external users do not get their own namespace and a personal fork is thus not possible.		This is a limitation of GitLab service at UiB. The external users do not get their own namespace and a personal fork is thus not possible.

	Instead, you can use a common development fork which is created by the project maintainers in subgroup [https://git.app.uib.no/pct/development pct/development].		Instead, you can use a common development fork which is created by the project maintainers in subgroup [https://git.app.uib.no/pct/development pct/development].

Mri083: /* How do I update a branch after fulfilled merge request? */

2021-03-17T07:06:43Z

How do I update a branch after fulfilled merge request?

← Older revision		Revision as of 07:06, 17 March 2021
Line 214:		Line 214:

	=== How do I update a branch after fulfilled merge request? ===		=== How do I update a branch after fulfilled merge request? ===
			''coming soon''

	=== How can I delete a branch ===		=== How can I delete a branch ===
	A branch is deleted using <code>branch</code>-command with option <code>-d</code> or <code>-D</code>, the latter ignoring the check for loss of content, namely if the branch state is already available in other branches.		A branch is deleted using <code>branch</code>-command with option <code>-d</code> or <code>-D</code>, the latter ignoring the check for loss of content, namely if the branch state is already available in other branches.

Mri083: /* Create access token */

2021-03-05T07:22:06Z

Create access token

← Older revision		Revision as of 07:22, 5 March 2021
Line 22:		Line 22:
	# Store the token in a safe place or configure the relevant application for accessing the repository with this token immediately		# Store the token in a safe place or configure the relevant application for accessing the repository with this token immediately

	'''Caution!''': Everybody who has the token can use it, make sure that it does not leak. Usually, tokens are used to ~~allo~~ external apps and tools access to do their job. Such apps store the token as secrets and do not display tokens to the outside.		'''Caution!''': Everybody who has the token can use it, make sure that it does not leak. Usually, tokens are used to allow external apps and tools access to do their job. Such apps store the token as secrets and do not display tokens to the outside.

	Hints:		Hints:

Mri083: /* Create access token */

2021-03-05T07:21:32Z

Create access token

← Older revision		Revision as of 07:21, 5 March 2021
Line 22:		Line 22:
	# Store the token in a safe place or configure the relevant application for accessing the repository with this token immediately		# Store the token in a safe place or configure the relevant application for accessing the repository with this token immediately

	* '''Caution''': Everybody who has the token can use it, make sure that it does not leak. Usually, tokens are used to allo external apps and tools access to do their job. Such apps store the token as secrets and do not display tokens to the outside.		'''Caution!''': Everybody who has the token can use it, make sure that it does not leak. Usually, tokens are used to allo external apps and tools access to do their job. Such apps store the token as secrets and do not display tokens to the outside.

	Hints:		Hints:

Mri083: /* Create access token */

2021-03-05T07:21:14Z

Create access token

← Older revision		Revision as of 07:21, 5 March 2021
Line 21:		Line 21:
	# click <span style="color:white; background:#006400; bold">Create personal access token</span>		# click <span style="color:white; background:#006400; bold">Create personal access token</span>
	# Store the token in a safe place or configure the relevant application for accessing the repository with this token immediately		# Store the token in a safe place or configure the relevant application for accessing the repository with this token immediately

			* '''Caution''': Everybody who has the token can use it, make sure that it does not leak. Usually, tokens are used to allo external apps and tools access to do their job. Such apps store the token as secrets and do not display tokens to the outside.

	Hints:		Hints:
	* Create access tokens only for the scope with the minimal access permissions required for your purpose		* Create access tokens only for the scope with the minimal access permissions required for your purpose
	* Keep in mind: the token is only visible in the web interface after creation, you can not get it later		* Keep in mind: the token is only visible in the web interface after creation, you can not get it later
	* Unused tokens should be revoked as soon as possible		* Unused tokens should be revoked as soon as possible, or better, specify expiration date

	== Create repository clone ==		== Create repository clone ==

Mri083: /* How can I delete a branch */

2021-03-04T14:58:03Z

How can I delete a branch

@@ Line 213: / Line 213: @@
 === How do I update a branch after fulfilled merge request? ===
 === How can I delete a branch ===
 == Merge request ==

Mri083: /* How can I make a backup of a branch */

2021-03-04T14:48:20Z

How can I make a backup of a branch

← Older revision		Revision as of 14:48, 4 March 2021
Line 201:		Line 201:

	=== How can I make a backup of a branch ===		=== How can I make a backup of a branch ===
	~~coming soon~~		If you are starting to do changes to a branch, e.g. rebasing and resolving conflicts, it's good to make a copy of the branch.

			Simply create a new branch from the current one, and
			git branch backup_feature

			Once you have done the changes, check if there is any difference to the backup
			git diff backup_feature

			After the work has been finished its advisable to remove the backup branch.

	=== How do I update a branch after fulfilled merge request? ===		=== How do I update a branch after fulfilled merge request? ===
	=== How can I delete a branch ===		=== How can I delete a branch ===

Mri083: /* I have a clone of the main repository and want to connect it now to my fork? */

2021-03-04T14:33:38Z

I have a clone of the main repository and want to connect it now to my fork?

@@ Line 132: / Line 132: @@
      upstream	git@git.app.uib.no:pct/pct-online.git (fetch)
      upstream	git@git.app.uib.no:pct/pct-online.git (push)
 == Working with clones ==

Mri083: /* Which rules should I obey for working with the fork? */

2021-02-23T11:35:53Z

Which rules should I obey for working with the fork?

← Older revision		Revision as of 11:35, 23 February 2021
Line 74:		Line 74:
	* add your colleagues as developers to share the code with them. To simply allow read access for the project members add group '''pct''' with ''Reporter''-role.		* add your colleagues as developers to share the code with them. To simply allow read access for the project members add group '''pct''' with ''Reporter''-role.

	[[File:GitLab-fork-members-illustration.png\|800px]]		:: [[File:GitLab-fork-members-illustration.png \| 1200px]]

			* <span id="Select Fast-forward merge">select '''Fast-forward merge'''</span> for your fork in <code>Settings</code> -> <code>General</code> -> <code>MergeRequests</code>

			:: [[File:GitLab fork-setting forward-merge.png \| 800px]]

	=== How can I make a clone of a project in my fork? ===		=== How can I make a clone of a project in my fork? ===

Mri083: /* Which rules should I obey for working with the fork? */

2021-02-23T08:04:49Z

Which rules should I obey for working with the fork?

← Older revision		Revision as of 08:04, 23 February 2021
Line 72:		Line 72:
	* if you start a new feature, and it's expected to take a while, make a ''feature'' branch, e.g. ''dev-feature'' and give the feature a name		* if you start a new feature, and it's expected to take a while, make a ''feature'' branch, e.g. ''dev-feature'' and give the feature a name
	* synchronize regularly to the main repository by rebasing (tutorial coming soon)		* synchronize regularly to the main repository by rebasing (tutorial coming soon)
	* add your colleagues as developers to share the code with them~~, or to~~ simply ~~give~~ read access for the project members add group '''pct''' with ''Reporter''-role.		* add your colleagues as developers to share the code with them. To simply allow read access for the project members add group '''pct''' with ''Reporter''-role.

	[[File:GitLab-fork-members-illustration.png\|800px]]		[[File:GitLab-fork-members-illustration.png\|800px]]