4-1-you-make-your-repo.md 2.66 KB
Newer Older
1
2
3
---
layout: default
title: 4.1 Make a repository
4
5
parent: Tutorials
grand_parent: Git and GitLab
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
has_children: false
nav_order: 11
---


# Make a GitLab repository
{: .fs-8 }

Make your own basic documentation repository
{: .fs-6 .fw-300 }

---

## 1. Make your GitLab repository

Coming soon
{: .label .label-yellow }
**This documentation needs to be updated for GitLab**

Create a new repository for your documentation, code or pages site by going to your repositories and selecting "New".

Next git it a name, description, and add a README file. I've chosen not to add a license here as I have a preference for one which is not in the list of default licenses provided by GitHub.

Click "Create Repository" Ta-da! You have a repository! 🎉

![gif-make-repo](../../img/gifs/create-repo.gif)

## 2. Update your README.md

Your README is your landing page for your repository on GitHub. Depending on the Pages theme you chose, it may also be rendered as the "home" page on your site.

Your README should contain all the information someone needs to understand what your project is about and how they can contribute. Some suggested section headings for your README are below.

- Welcome
- What are we doing
  - The problem
  - The solution
- Who are we
- What do we need
- Contact Us
- Find out more
- Thank you

To get a quick outline of the README structure (and to differentiate it from the one automatically created by GitHub), I have chosen to edit the page in GitHub directly, and add the section headings in [Markdown](https://github.com/adam-p/markdown-here/wiki/Markdown-Cheatsheet).

To save your changes, describe what you did in the commit message, then press "commit"

![gif-update-readme](../../img/gifs/update-readme.gif)

## 3. Create a LICENSE.md

A license file is essential to indicate to others how you want your repository to be reused and credited.

To get the license file in place, I'm going to use the "add file" function and add a title and a link to the CC-BY legal wording.

To save your changes, describe what you did in the commit message, then press "commit"

![gif-add-license](../../img/gifs/add-license.gif)

## 4. Create a CONTRIBUTING.md

A contributing file is essential to let other know what you would like help with and how you would like people to contribute.

To get the contributing file in place, I'm going to use the "add file" function and simply add a title. I'll fill in the details later!

To save your changes, describe what you did in the commit message, then press "commit"

![gif-add-contributing](../../img/gifs/add-contributing.gif)

Have a look at our [what to include in a repository](../analysis/repo-include.md) guide for a more complete description of these files.