debian-mirror-gitlab/doc/user/project/repository/index.md

296 lines
11 KiB
Markdown
Raw Normal View History

2019-10-12 21:52:04 +05:30
---
2020-10-24 23:57:45 +05:30
stage: Create
group: Source Code
2021-02-22 17:27:13 +05:30
info: To determine the technical writer assigned to the Stage/Group associated with this page, see https://about.gitlab.com/handbook/engineering/ux/technical-writing/#assignments
2019-10-12 21:52:04 +05:30
---
2021-03-11 19:13:27 +05:30
# Repository **(FREE)**
2017-09-10 17:25:29 +05:30
A [repository](https://git-scm.com/book/en/v2/Git-Basics-Getting-a-Git-Repository)
2021-09-04 01:27:46 +05:30
is where you store your code and make changes to it. Your changes are tracked with version control.
Each [project](../index.md) contains a repository.
2017-09-10 17:25:29 +05:30
## Create a repository
2021-09-04 01:27:46 +05:30
To create a repository, you can:
- [Create a project](../../../user/project/working_with_projects.md#create-a-project) or
- [Fork an existing project](forking_workflow.md).
## Add files to a repository
You can add files to a repository:
- When you create a project.
- After you create a project:
- By using [the web editor](web_editor.md).
- [From the command line](../../../gitlab-basics/command-line-commands.md).
## Commit changes to a repository
You can [commit your changes](https://git-scm.com/book/en/v2/Git-Basics-Recording-Changes-to-the-Repository),
to a branch in the repository. When you use the command line, you can commit multiple times before you push.
- **Commit message:**
2021-11-11 11:23:49 +05:30
A commit message identifies what is being changed and why.
2021-09-04 01:27:46 +05:30
In GitLab, you can add keywords to the commit
message to perform one of the following actions:
- **Trigger a GitLab CI/CD pipeline:**
2021-09-30 23:02:18 +05:30
If the project is configured with [GitLab CI/CD](../../../ci/index.md),
2021-09-04 01:27:46 +05:30
you trigger a pipeline per push, not per commit.
- **Skip pipelines:**
2021-12-11 22:18:48 +05:30
Add the [`ci skip`](../../../ci/pipelines/index.md#skip-a-pipeline) keyword to
2021-09-04 01:27:46 +05:30
your commit message to make GitLab CI/CD skip the pipeline.
- **Cross-link issues and merge requests:**
Use [cross-linking](../issues/crosslinking_issues.md#from-commit-messages)
to keep track of related parts of your workflow.
If you mention an issue or a merge request in a commit message, they are displayed
on their respective thread.
- **Cherry-pick a commit:**
In GitLab, you can
2021-11-11 11:23:49 +05:30
[cherry-pick a commit](../merge_requests/cherry_pick_changes.md#cherry-pick-a-commit)
2021-09-04 01:27:46 +05:30
from the UI.
- **Revert a commit:**
2021-11-11 11:23:49 +05:30
[Revert a commit](../merge_requests/revert_changes.md#revert-a-commit)
2021-09-04 01:27:46 +05:30
from the UI to a selected branch.
- **Sign a commit:**
Use GPG to [sign your commits](gpg_signed_commits/index.md).
## Clone a repository
You can [clone a repository by using the command line](../../../gitlab-basics/start-using-git.md#clone-a-repository).
Alternatively, you can clone directly into a code editor.
### Clone and open in Apple Xcode
Projects that contain a `.xcodeproj` or `.xcworkspace` directory can be cloned
into Xcode on macOS.
1. From the GitLab UI, go to the project's overview page.
1. Select **Clone**.
1. Select **Xcode**.
The project is cloned onto your computer and you are
prompted to open XCode.
### Clone and open in Visual Studio Code
> [Introduced](https://gitlab.com/gitlab-org/gitlab/-/issues/220957) in GitLab 13.10.
2021-12-11 22:18:48 +05:30
All projects can be cloned into Visual Studio Code from the GitLab user interface, but you
can also install the [GitLab Workflow VS Code extension](vscode.md) to clone from
Visual Studio Code:
2021-09-04 01:27:46 +05:30
2021-12-11 22:18:48 +05:30
- From the GitLab interface:
1. Go to the project's overview page.
1. Select **Clone**.
1. Under either the **HTTPS** or **SSH** method, select **Clone with Visual Studio Code**.
1. Select a folder to clone the project into.
2021-09-04 01:27:46 +05:30
2021-12-11 22:18:48 +05:30
After Visual Studio Code clones your project, it opens the folder.
- From Visual Studio Code, with the [extension](vscode.md) installed, use the
extension's [`Git: Clone` command](https://marketplace.visualstudio.com/items?itemName=GitLab.gitlab-workflow#clone-gitlab-projects).
2017-09-10 17:25:29 +05:30
2021-09-04 01:27:46 +05:30
## Download the code in a repository
2017-09-10 17:25:29 +05:30
2022-03-02 08:16:31 +05:30
> Support for [including Git LFS blobs](../../../topics/git/lfs#lfs-objects-in-project-archives) was [introduced](https://gitlab.com/gitlab-org/gitlab/-/issues/15079) in GitLab 13.5.
2017-09-10 17:25:29 +05:30
2021-09-04 01:27:46 +05:30
You can download the source code that's stored in a repository.
2018-03-17 18:26:18 +05:30
2021-09-04 01:27:46 +05:30
1. Above the file list, select the download icon (**{download}**).
1. From the options, select the files you want to download.
2020-04-22 19:07:51 +05:30
2021-09-04 01:27:46 +05:30
- **Source code:**
Download the source code from the current branch you're viewing.
Available extensions: `zip`, `tar`, `tar.gz`, and `tar.bz2`.
- **Directory:**
Download a specific directory. Visible only when you view a subdirectory.
Available extensions: `zip`, `tar`, `tar.gz`, and `tar.bz2`.
- **Artifacts:**
Download the artifacts from the latest CI job.
2020-04-22 19:07:51 +05:30
2021-09-04 01:27:46 +05:30
## Repository languages
2017-09-10 17:25:29 +05:30
2021-09-04 01:27:46 +05:30
For the default branch of each repository, GitLab determines which programming languages
are used. This information is displayed on the **Project information** page.
2017-09-10 17:25:29 +05:30
2021-09-04 01:27:46 +05:30
![Repository Languages bar](img/repository_languages_v12_2.gif)
2017-09-10 17:25:29 +05:30
2021-09-04 01:27:46 +05:30
When new files are added, this information can take up to five minutes to update.
2017-09-10 17:25:29 +05:30
2021-09-04 01:27:46 +05:30
### Add repository languages
2017-09-10 17:25:29 +05:30
2021-09-04 01:27:46 +05:30
Not all files are detected and listed on the **Project information** page. Documentation,
vendor code, and most markup languages are excluded.
2017-09-10 17:25:29 +05:30
2021-09-04 01:27:46 +05:30
You can change this behavior by overriding the default settings.
2017-09-10 17:25:29 +05:30
2021-09-04 01:27:46 +05:30
1. In your repository's root directory, create a file named `.gitattributes`.
1. Add a line that tells GitLab to include files of this type. For example,
to enable `.proto` files, add the following code:
2017-09-10 17:25:29 +05:30
2021-09-04 01:27:46 +05:30
```plaintext
*.proto linguist-detectable=true
```
2018-03-17 18:26:18 +05:30
2021-09-04 01:27:46 +05:30
View a list of
[supported data types](https://github.com/github/linguist/blob/master/lib/linguist/languages.yml).
2018-03-17 18:26:18 +05:30
2021-09-04 01:27:46 +05:30
This feature can use excessive CPU.
For more information, see the [troubleshooting section](#repository-languages-excessive-cpu-use).
2018-12-13 13:39:08 +05:30
2021-09-04 01:27:46 +05:30
### Supported markup languages
2018-12-13 13:39:08 +05:30
2021-09-04 01:27:46 +05:30
If your file has one of the following file extensions, GitLab renders the
contents of the file's [markup language](https://en.wikipedia.org/wiki/Lightweight_markup_language) in the UI.
2018-12-13 13:39:08 +05:30
| Markup language | Extensions |
| --------------- | ---------- |
| Plain text | `txt` |
| [Markdown](../../markdown.md) | `mdown`, `mkd`, `mkdn`, `md`, `markdown` |
2020-03-13 15:44:24 +05:30
| [reStructuredText](https://docutils.sourceforge.io/rst.html) | `rst` |
2019-09-04 21:01:54 +05:30
| [AsciiDoc](../../asciidoc.md) | `adoc`, `ad`, `asciidoc` |
2019-12-04 20:38:33 +05:30
| [Textile](https://textile-lang.com/) | `textile` |
2021-01-03 14:25:43 +05:30
| [Rdoc](http://rdoc.sourceforge.net/doc/index.html) | `rdoc` |
2020-06-23 00:09:42 +05:30
| [Org mode](https://orgmode.org/) | `org` |
2018-12-13 13:39:08 +05:30
| [creole](http://www.wikicreole.org/) | `creole` |
2020-06-23 00:09:42 +05:30
| [MediaWiki](https://www.mediawiki.org/wiki/MediaWiki) | `wiki`, `mediawiki` |
2018-12-13 13:39:08 +05:30
2021-09-04 01:27:46 +05:30
### README and index files
2018-12-13 13:39:08 +05:30
2021-09-04 01:27:46 +05:30
When a `README` or `index` file is present in a repository, GitLab renders its contents.
These files can either be plain text or have the extension of a
[supported markup language](#supported-markup-languages).
2018-12-13 13:39:08 +05:30
2021-09-04 01:27:46 +05:30
- When both a `README` and an `index` file are present, the `README` always
takes precedence.
- When multiple files have the same name but a different extension, the files are
ordered alphabetically. Any file without an extension is ordered last.
For example, `README.adoc` takes precedence over `README.md`, and `README.rst`
takes precedence over `README`.
2018-05-09 12:01:36 +05:30
2020-01-01 13:55:28 +05:30
### OpenAPI viewer
2020-06-23 00:09:42 +05:30
> [Introduced](https://gitlab.com/gitlab-org/gitlab/-/issues/19515) in GitLab 12.6.
2020-01-01 13:55:28 +05:30
2021-09-04 01:27:46 +05:30
GitLab can render OpenAPI specification files. The filename
must include `openapi` or `swagger` and the extension must be `yaml`,
2020-01-01 13:55:28 +05:30
`yml`, or `json`. The following examples are all correct:
- `openapi.yml`
- `openapi.yaml`
- `openapi.json`
- `swagger.yml`
- `swagger.yaml`
- `swagger.json`
- `gitlab_swagger.yml`
- `openapi_gitlab.yml`
- `OpenAPI.YML`
- `openapi.Yaml`
- `openapi.JSON`
- `openapi.gitlab.yml`
- `gitlab.openapi.yml`
2021-09-04 01:27:46 +05:30
To render an OpenAPI file:
2020-01-01 13:55:28 +05:30
2021-09-04 01:27:46 +05:30
1. Go to the OpenAPI file in your repository.
1. Between the **Display source** and **Edit** buttons, select **Display OpenAPI**. When an OpenAPI file is found, it replaces the
**Display rendered file** button.
2020-01-01 13:55:28 +05:30
2021-09-04 01:27:46 +05:30
## Repository size
2017-09-10 17:25:29 +05:30
2021-09-04 01:27:46 +05:30
The **Project information** page shows the size of all files in the repository. The size is
updated, at most, every 15 minutes. The file size includes repository files, artifacts, and LFS.
2017-09-10 17:25:29 +05:30
2021-09-04 01:27:46 +05:30
The size can differ slightly from one instance to another due to compression, housekeeping, and other factors.
2017-09-10 17:25:29 +05:30
2021-09-04 01:27:46 +05:30
Administrators can set a [repository size limit](../../admin_area/settings/account_and_limit_settings.md).
[GitLab sets the size limits for GitLab.com](../../gitlab_com/index.md#account-and-limit-settings).
2017-09-10 17:25:29 +05:30
2021-09-04 01:27:46 +05:30
## Repository contributor graph
2017-09-10 17:25:29 +05:30
2021-09-04 01:27:46 +05:30
All code contributors are displayed under your project's **Repository > Contributors**.
2017-09-10 17:25:29 +05:30
2021-09-04 01:27:46 +05:30
The graph shows the contributor with the most commits to the fewest.
2017-09-10 17:25:29 +05:30
![contributors to code](img/contributors_graph.png)
2021-09-04 01:27:46 +05:30
## Repository history graph
2017-09-10 17:25:29 +05:30
2021-09-04 01:27:46 +05:30
A repository graph displays a visual history of the repository network, including branches and merges.
This graph can help you visualize the Git flow strategy used in the repository.
2018-03-17 18:26:18 +05:30
2021-09-04 01:27:46 +05:30
Go to your project's **Repository > Graph**.
2021-03-08 18:12:59 +05:30
2021-09-04 01:27:46 +05:30
![repository Git flow](img/repo_graph.png)
2021-03-11 19:13:27 +05:30
2021-09-04 01:27:46 +05:30
## What happens when a repository path changes
2021-03-11 19:13:27 +05:30
2021-09-04 01:27:46 +05:30
When a repository path changes, GitLab handles the transition from the
old location to the new one with a redirect.
2021-03-11 19:13:27 +05:30
2021-09-04 01:27:46 +05:30
When you [rename a user](../../profile/index.md#change-your-username),
[change a group path](../../group/index.md#change-a-groups-path), or [rename a repository](../settings/index.md#renaming-a-repository):
2021-03-11 19:13:27 +05:30
2021-09-04 01:27:46 +05:30
- URLs for the namespace and everything under it, like projects, are
redirected to the new URLs.
- Git remote URLs for projects under the
namespace redirect to the new remote URL. When you push or pull to a
repository that has changed location, a warning message to update
your remote is displayed. Automation scripts or Git clients continue to
work after a rename.
2021-03-11 19:13:27 +05:30
- The redirects are available as long as the original path is not claimed by
2021-09-04 01:27:46 +05:30
another group, user, or project.
2021-03-11 19:13:27 +05:30
2022-01-26 12:08:38 +05:30
## Related topics
2021-12-11 22:18:48 +05:30
2022-01-26 12:08:38 +05:30
- [GitLab Workflow VS Code extension](vscode.md).
- To lock files and prevent change conflicts, use [file locking](../file_lock.md).
- [Repository API](../../../api/repositories.md).
- [Find files](file_finder.md) in a repository.
- [Branches](branches/index.md).
- [File templates](web_editor.md#template-dropdowns).
- [Create a directory](web_editor.md#create-a-directory).
- [Start a merge request](web_editor.md#tips).
- [Find file history](git_history.md).
- [Identify changes by line (Git blame)](git_blame.md).
- [Use Jupyter notebooks with GitLab](jupyter_notebooks/index.md).
2021-12-11 22:18:48 +05:30
2021-06-08 01:23:25 +05:30
## Troubleshooting
### Repository Languages: excessive CPU use
2021-09-04 01:27:46 +05:30
To determine which languages are in a repository's files, GitLab uses a Ruby gem.
When the gem parses a file to determine which type it is, [the process can use excessive CPU](https://gitlab.com/gitlab-org/gitaly/-/issues/1565).
2021-06-08 01:23:25 +05:30
The gem contains a [heuristics configuration file](https://github.com/github/linguist/blob/master/lib/linguist/heuristics.yml)
2021-09-04 01:27:46 +05:30
that defines which file extensions must be parsed.
2021-06-08 01:23:25 +05:30
2021-09-04 01:27:46 +05:30
Files with the `.txt` extension and XML files with an extension not defined by the gem can take excessive CPU.
2021-06-08 01:23:25 +05:30
2021-09-04 01:27:46 +05:30
The workaround is to specify the language to assign to specific file extensions.
2021-06-08 01:23:25 +05:30
The same approach should also allow misidentified file types to be fixed.
2021-09-04 01:27:46 +05:30
1. Identify the language to specify. The gem contains a [configuration file for known data types](https://github.com/github/linguist/blob/master/lib/linguist/languages.yml).
To add an entry for text files, for example:
2021-06-08 01:23:25 +05:30
```yaml
Text:
type: prose
wrap: true
aliases:
- fundamental
- plain text
extensions:
- ".txt"
```
1. Add or modify `.gitattributes` in the root of your repository:
2019-10-12 21:52:04 +05:30
2021-06-08 01:23:25 +05:30
```plaintext
*.txt linguist-language=Text
```
2019-10-12 21:52:04 +05:30
2021-09-04 01:27:46 +05:30
`*.txt` files have an entry in the heuristics file. This example prevents parsing of these files.