Commit 1e41563e authored by Nicolas Descostes's avatar Nicolas Descostes
Browse files

tmp commit before continuing step 7

parent 85794e73
......@@ -63,6 +63,7 @@ Automated version control systems are nothing new. Tools like RCS, CVS, or Subve
![log](pictures/First-steps-on-embl-git/step1.png)
2. Explore the welcome page
![Welcome](pictures/First-steps-on-embl-git/step2.png)
......@@ -71,6 +72,7 @@ Automated version control systems are nothing new. Tools like RCS, CVS, or Subve
* B: When creating a project, you can define access rights (**private, internal, public**; see below). This tab will restrict the view to your projects that are **private**.
* C: Search bar, search for a particular project by keywords.
* D: Create a new project (see below).
3. Explore projects
......@@ -80,13 +82,42 @@ Automated version control systems are nothing new. Tools like RCS, CVS, or Subve
* B: Display the repositories by 'last updated', 'name', 'oldest updated', and other criteria.
* C: Display the repositories whether they are 'public', 'internal' or 'private'.
* D: The 'New project' icon is always accessible from the interface (see next step).
4. Create a new project
![projects](pictures/First-steps-on-embl-git/step4.png)
![new project](pictures/First-steps-on-embl-git/step4.png)
* A: Enter your project name such as 'Demo Repo'.
* B: A repository slug is a URL-friendly version of a repository name, you can see that upper-case letters and space were removed ('demo-repo').
* C: Enter a description of the repository such as 'first creation of a git repository'. This will be displayed under your repository name on the welcome page.
* D: Choose the visibility level of the repository. 'private' means that only you and other owners (that you could invite) can see the repository; 'internal' means that only people from embl can see the repository; and 'public' makes the repository readable to anybody.
* E: Initialize the repository with a markdown document called 'README.md'. Select this option. The description (see point C) and the title of your repository will appear in this document by default.
* F: Click 'Create project'.
5. Explore the repository interface
![repository](pictures/First-steps-on-embl-git/step5.png)
* A: Title of the repository. The lock icon indicates that the repository is private.
* B: You will see later on what *commit* and *branches* means. Aside from the indicated size of the repository (depending on the files stored in it), you can add a license (defining the conditions of utilization of you documents and code) and some searchable tags.
* C: The bell icon enables to define how you should be notified concerning modifications made to the repository. Star is functionning as 'likes' on twitter or facebook. The clone button is what you will use to import the repository on your computer or in a development interface. The fork button enables you to clone any (non-private) repository in order to modify it.
* D: Indicate the branch on which you are (see below on how to create and use branches). The '+' icon enables to add new files or folders; you will almost never use this button. The history displays modifications made on your repository and the 'down arrow' icon is a download button.
* E: This secton contains all the folders and files of your repository. For the moment there is only one file: 'README.md'. The 'Last commit' column displays the last modification message for each file. 'Last update' indicates when a particular modification happened.
* F: The README file, it is usually used to create the documentation of your repository.
6. Edit README.md
![readme modification](pictures/First-steps-on-embl-git/step6.png)
7. Modify and commit
![modify and commit](pictures/First-steps-on-embl-git/step7.png)
* A: Indicate the edited file.
* B: Modificaton of the document. Here the sentence is 'Doing my first modification'.
* C:
A repository slug is a URL-friendly version of a repository name,
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
......
Supports Markdown
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment