---
eleventyNavigation:
  key: FirstRepository
  title: Your First Repository
  parent: GettingStarted
  order: 30
---

Almost everything you can do on Codeberg starts in a repository. Think of a repository as a home for your project, where all of its source code can be organized using Git and which also contains optional features like an issue tracker and wiki.

This article will lead you through creating your first repository on Codeberg, connecting your local development environment and making your first source code commit.

## Creating a Repository
> A note to more advanced users: It is currently not possible to use Push-to-Create to push a fresh repository onto Codeberg.

To create a new repository, you need be logged in to your account on Codeberg.org.

After login, you can use one of the two buttons shown in the two following screenshots to create a new repository:

<picture>
  <source srcset="/assets/images/getting-started/first-repository/create-repo.webp" type="image/webp">
  <img src="/assets/images/getting-started/first-repository/create-repo.png" alt="Creating a Repository">
</picture>

This will lead you to this form:

<picture>
  <source srcset="/assets/images/getting-started/first-repository/create-repo-2.webp" type="image/webp">
  <img src="/assets/images/getting-started/first-repository/create-repo-2.png" alt="New Repository Form">
</picture>

Here's an explanation of the form's fields:

- **Owner** Here, you can specify, whether you want this to be your own personal project or whether you want it to be part of an organization that you belong to
- **Repository name** A name for your repository (which will also be part of its the path, in this case `https://codeberg.org/knut/foobar`)
- **Visibility** Repositories are either *public* or *private*, where public means that everyone will be able to see your repository, while your private repositories can only be accessed by you and your collaborators (see [Invite Collaborators](/collaborating/invite-collaborators))
- **Description** A short description that appears next to your repository's name where appropriate
- **Template** Occasionally you may want to generate your repository from an existing template repository. In that case, you can specify that template here. Otherwise, simply leave this field empty.
- **Issue Labels** If you want to initialize your project's issue tracker with a set of labels that you can use to categorize issues, you can choose one here. You don't have to choose this right away though, as you can choose and modify issue labels at a later time too.
- **.gitignore** A [.gitignore](https://git-scm.com/docs/gitignore) file defines which files Git should not keep track of. This is for example useful to prevent project configuration files or binaries to be checked into version control. You can choose to add a pre-defined file matching the programming language you use now, or add one manually at a later time.
- **License** Here, you can choose from a list of FSF/OSI approved licenses. A `LICENSE` file will then be added to the repository. For some help on choosing the correct license, check for example the [GNU Operating System](https://www.gnu.org/licenses/license-list), the [Open Source Initiative](https://opensource.org/licenses) or the [choosealicense.com](https://choosealicense.com/) websites.
- **README** is the first file one should read when accessing a project. It also happens to be the first one displayed when accessing a repository, a bit like the "homepage" of your repository. On Codeberg, this is interpreted as a [Markdown](/markdown) file.
- **Initialize repository** To add the `LICENSE`, `README` and `.gitignore` files mentioned above to your new repository, make sure you tick this box.
- **Default branch** Using this field, you can choose how to name the default branch of your Git repository. We recommend you use the predefined default.

It's okay to only specify owner and repository name, if you want to get started quickly.
After filling out the form, click the green "Create Repository" button on the bottom of the form.

You should now see a screen similar to the one below. If you haven't chosen to auto-generate `LICENSE`, `README` and `.gitignore` the screen might show instructions instead, which will vanish after [your first commit](#first-commit).

<picture>
  <source srcset="/assets/images/getting-started/first-repository/create-repo-3.webp" type="image/webp">
  <img src="/assets/images/getting-started/first-repository/create-repo-3.png" alt="Repository Main View">
</picture>

Here's what the most important buttons of this screen do:

- **Repository Settings (1)** is where you can make adjustments to your repository set-up, such as setting a project website, changing the repository description, enabling/disabling wiki and issue tracker or deleting the repository. You may want to give this site a visit right now, to get an overview of your options.
- **The Watch, Star and Fork buttons (2)** enable you to interact with other people's repositories. While they don't do much for your own repository, when visiting another user's repository, you can click on "Watch" to get notified about everything important happening in that repository, "Star" to show the user your appreciation (and to help other users find interesting projects more quickly) and "Fork" to create your own copy of the repository, for example to make modifications that you want to share with the original author.
- **The Repository Tabs (3)** contain links to every important feature within your repository:
  - **Code** lets you browse through all versions of your code
  - **Issues** is a very important communication tool between you, your users and your contributors. Think of it as part bug-tracker, part forum.
  For more information on this, have a look at [The Basics of Issue Tracking](/getting-started/issue-tracking-basics)
  - **Pull Requests** is where other users can ask you to include a change into your program
  - **Releases** is a space where you can upload finished versions of your program, including binaries
  - **Wiki** is a very basic wiki built into Gitea, the software Codeberg is based on
  - **Activity** calculates statistics about your project
- **Your repository's Git URLs** - use these to let Git know where to find your repository. Don't worry if that is a bit cryptic now - we will pick this up again in the following section.


## Connect a local repository to Codeberg
After creating a new repository, as laid out in the previous section, you can now move on to connect the repository with your local development copy.

In this guide, we'll focus on connecting to Codeberg via HTTP using Git on the command line, but note that there are multiple other ways to connect to Codeberg, as laid out in more detail in the articles:

- [Clone & Commit via HTTP](/git/clone-commit-via-http),
- [Clone & Commit via SSH](/git/clone-commit-via-ssh) and
- [Clone & Commit via Web](/git/clone-commit-via-web)

> Although we use HTTP in this Getting Started guide, it is a good idea to [setup SSH-based authentication](/security/ssh-key) once you feel confident to do so

### Option A: Clone the newly created, empty repository
If you want to start a fresh project (so if you don't already have source code that you want to upload to Codeberg), the quickest way to get started is to clone your newly created repository like this:

#### 1. Navigate to your local workspace (optional)
If you're just getting started, it's a good idea to keep your projects neatly sorted in a dedicated directory, like in this example:

```bash
knut@iceberg:~$ mkdir repositories
knut@iceberg:~$ cd repositories
knut@iceberg:~/repositories$
```

#### 2. Execute `git clone`
To clone your newly created repository, you should now execute `git clone` with the URL that is shown in your repository:

<picture>
  <source srcset="/assets/images/getting-started/first-repository/repo-url.webp" type="image/webp">
  <img src="/assets/images/getting-started/first-repository/repo-url.png" alt="Repository Clone URL">
</picture>

```bash
knut@iceberg:~/repositories$ git clone https://codeberg.org/knut/foobar
Cloning into 'foobar'...
remote: Enumerating objects: 4, done.
remote: Counting objects: 100% (4/4), done.
remote: Compressing objects: 100% (3/3), done.
remote: Total 4 (delta 0), reused 0 (delta 0)
Unpacking objects: 100% (4/4), 11.94 KiB | 764.00 KiB/s, done.
```

#### 3. Navigate to the cloned repository
After cloning, the repository should now be in a new subdirectory with the same name as your repository, in this case `foobar`.

```bash
knut@iceberg:~/repositories$ cd foobar
knut@iceberg:~/repositories/foobar$ ls
LICENSE  README.md
```


### Option B: Connect an existing local source tree
If you already have written source code that you now would like to upload to Codeberg, follow these steps:

#### 1. Initialize a Git Repository
Do this first, unless you already have a Git Repository initialized in your local source tree:

```bash
knut@iceberg:~/my-project$ git init
Initialized empty Git repository in /home/knut/my-project/.git/
```

#### 2. Add Codeberg as the repository's origin
Now, you need to tell Git where to push your changes. You do that by specifying Codeberg as a remote.

> In this example, we'll specify Codeberg as the `origin` remote. You can name your remote any other way, especially if you already have an `origin`, but `origin` is the recommended name for the main remote repository.

```bash
knut@iceberg:~/my-project$ git remote add origin https://codeberg.org/knut/foobar
```

This command has no output on the command line.


<a name="first-commit"></a>
## Making your first commit
Now that you've connected your repository to your local development copy, it is time to make your first commit.

> If you haven't auto-generated them when creating the repository, it is now a good idea to add the `LICENSE` and `README.md` files. Just put them in your local development copy's directory and add them to your commit, as shown below.

#### 1. Create or edit a file
Let's modify the auto-generated `README.md` file.

> If you haven't auto-generated `README.md`, the following commands will still work fine, but create a new file containing only `Hello World!` instead

```bash
knut@iceberg:~/repositories/foobar$ echo "Hello World!" >> README.md
knut@iceberg:~/repositories/foobar$ cat README.md
# foobar

Hello World!
```

If you now ask Git about your repository's status, you should see a similar screen to this:

```bash
knut@iceberg:~/repositories/foobar$ git status
On branch main
Your branch is up to date with 'origin/main'.

Changes not staged for commit:
  (use "git add <file>..." to update what will be committed)
  (use "git restore <file>..." to discard changes in working directory)
	modified:   README.md

no changes added to commit (use "git add" and/or "git commit -a")
```

You can go ahead and modify or create more files, if you want.

#### 2. Add changes to your commit
Next, you should add each changed file that you want to be part of your commit using `git add`:

```bash
knut@iceberg:~/repositories/foobar$ git add README.md
```

The `git add` command has no output on the command line.

> If you want to add all changed files in your source tree, you can run `git add .` but **be careful** as this might add unwanted files as well, so it's a good idea to double-check by running `git status` before committing.

#### 3. Commit your changes
By committing your changes, you create a new step in the version history of your program. They act like snapshots of your program's state at a given point of time, and you will later be able to jump back and forth between them.

> It is recommended to keep commits small and focused, so that, if necessary, they can be reverted or easily adapted into another context without too many side-effects

To commit you added changes, run `git commit` and specify a commit message, which will later help you (and others) to identify that commit when looking back at your version history.

```bash
knut@iceberg:~/repositories/foobar$ git commit -m "My first commit on Codeberg"
[main 1e12979] My first commit on Codeberg
 1 file changed, 1 insertion(+)
```

If you look at the version history of your program using `git log`, you may now see something similar to this:

```bash
knut@iceberg:~/repositories/foobar$ git log
commit 1e1297929c8c74d9a439fa71c1f0ffe1dbf3d5ad (HEAD -> main)
Author: Knut <knut@noreply.codeberg-test.org>
Date:   Sat Sep 26 14:01:00 2020 +0200

    My first commit on Codeberg

commit c75b50920e3aa7a7ab3484e898fb3ad77132722a (origin/main, origin/HEAD)
Author: Knut <knut@noreply.codeberg-test.org>
Date:   Sat Sep 26 12:29:57 2020 +0200

    Initial commit
```

#### 4. Push your changes to Codeberg
If you're happy with the changes you made, the next step is to present them to the world by pushing them to Codeberg.org:

```bash
knut@iceberg:~/repositories/foobar$ git push -u origin main
Username for 'https://codeberg.org': knut
Password for 'https://knut@codeberg.org':
Enumerating objects: 5, done.
Counting objects: 100% (5/5), done.
Delta compression using up to 16 threads
Compressing objects: 100% (2/2), done.
Writing objects: 100% (3/3), 315 bytes | 315.00 KiB/s, done.
Total 3 (delta 0), reused 0 (delta 0)
remote: . Processing 1 references
remote: Processed 1 references in total
To https://codeberg.org/knut/foobar
   c75b509..1e12979  main -> main
Branch 'main' set up to track remote branch 'main' from 'origin'.
```

The `-u` option sets the upstream remote, which we want to be Codeberg.org, as configured previously.

The `main` argument sets the name of the branch onto which shall be pushed upstream. For this example, it should be the same branch name that you specified when creating the repository.

When connecting via HTTPS, git will ask you for your username and password, which you can enter interactively.

Refreshing the repository page, you should now see something like this:

<picture>
  <source srcset="/assets/images/getting-started/first-repository/hello-world.webp" type="image/webp">
  <img src="/assets/images/getting-started/first-repository/hello-world.png" alt="Hello World from first commit">
</picture>

Congratulations - you've just made your first source code contribution on Codeberg!

Now is a good time to [learn more about issue tracking](/getting-started/issue-tracking-basics)
