en_help.md

---
layout: page
title: Help on use
permalink: /help/
ref: help
lang: en
---

## How to use GitLab?
TODO: Browser sufficient for many things, installing Git locally.

## First steps
TODO: Rough overview, links to good resources for learning more (see below).

## Visibility of Projects (and groups?)
TODO: Meanings of *private*, *internal*, and *public*.

## User roles and permissions

If you include somebody as a project member, you have to decide what role they should have.
You can pick either *Guest*, *Reporter*, *Developer*, *Maintainer*, or *Owner*.
Each role is associated with an increasing set of permissions, see them [here in form of a table](https://gitlab.test.uni-giessen.de/help/user/permissions.md#project-members-permissions).

### Project permissions as Guest

Project members with the *Guest* role can
download the project,
leave comments,
view and pull project code,
view wiki pages,
create new issues,
see related issues,
create confidential issues,
and view the confidential issues they created themselves.

If **Public pipelines** is enabled in **Project Settings > CI/CD**, they can also
see a list of jobs,
see a job log,
and download and browse job artifacts.

### Project permissions as Reporter

Project members with the *Reporter* role has the same permissions as a *Guest*, and additionally can
create new branches,
push to non-protected branches,
force push to non-protected branches,
remove non-protected branches,
create new merge request,
assign merge requests,
label merge requests,
lock merge request threads,
manage/Accept merge requests,
create new environments,
stop environments,
add tags,
cancel and retry jobs,
create or update commit status,
update a container registry,
remove a container registry image,
create/edit/delete project milestones,
apply code change suggestions,
create and edit wiki pages, and
rewrite/remove Git tags.

### Project permissions as Developer

TODO 

### Project permissions as Maintainer

TODO 

### Project permissions as Owner

TODO 


## User groups
TODO: Group members and their roles and associated permissions.
TODO: Clarification that group projects won't be deleted when leaving JLU, as long as members exist in the group.

## Settings about private information
TODO: Setting of commit email address (in GitLab and locally), hiding of activity and profile, ...

## Last steps
TODO: Explanation when and what stuff gets deleted once you leave JLU (account data, *own* projects, ...) and what doesn't (group projects including issues and comments, commits, ...).
- Except for commits, stuff will be anonymized (transferred to the Ghost user).

## Further help
TODO: Useful links, maybe in categories.