Skip to content
Projects
Groups
Snippets
Help
Loading...
Help
Submit feedback
Contribute to GitLab
Sign in
Toggle navigation
M
mooc-rr-ressources
Project
Project
Details
Activity
Releases
Cycle Analytics
Repository
Repository
Files
Commits
Branches
Tags
Contributors
Graph
Compare
Charts
Issues
0
Issues
0
List
Board
Labels
Milestones
Merge Requests
4
Merge Requests
4
Wiki
Wiki
Snippets
Snippets
Members
Members
Collapse sidebar
Close sidebar
Activity
Graph
Charts
Create a new issue
Commits
Issue Boards
Open sidebar
Learning Lab
mooc-rr-ressources
Commits
7b693302
Commit
7b693302
authored
Nov 21, 2018
by
Marie-Gabrielle Dondon
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
typo + ajout balises #+BEGIN_CENTER, #+END_CENTER manquantes
parent
a007cab3
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
with
18 additions
and
6 deletions
+18
-6
gitlab.org
module2/ressources/gitlab.org
+18
-6
No files found.
module2/ressources/gitlab.org
View file @
7b693302
...
@@ -200,7 +200,9 @@ Here are other ways to learn Git through the command line:
...
@@ -200,7 +200,9 @@ Here are other ways to learn Git through the command line:
Now, let's start!
Now, let's start!
1. Obtain the repository URL
1. Obtain the repository URL
#+BEGIN_CENTER
[[file:rstudio_images/adresse_depot.png]]
[[file:rstudio_images/adresse_depot.png]]
#+END_CENTER
2. Cloning the repository
2. Cloning the repository
#+begin_src shell :results output :exports both
#+begin_src shell :results output :exports both
cd /the/directory/where/you/want/to/clone/your/repository
cd /the/directory/where/you/want/to/clone/your/repository
...
@@ -226,47 +228,57 @@ Now, let's start!
...
@@ -226,47 +228,57 @@ Now, let's start!
GitLab. The =git status= will indicate you whether files are
GitLab. The =git status= will indicate you whether files are
tracked/modified/committed/...
tracked/modified/committed/...
Let's assume you just created a
`fichier.txt`
file on the top of
Let's assume you just created a
=fichier.txt=
file on the top of
the =mooc-rr= directory.
the =mooc-rr= directory.
#+begin_src shell :results output :exports both
#+begin_src shell :results output :exports both
git status
git status
#+end_src
#+end_src
#+BEGIN_CENTER
[[file:gitlab_images/status1.png]]
[[file:gitlab_images/status1.png]]
#+END_CENTER
#+begin_src shell :results output :exports both
#+begin_src shell :results output :exports both
git add fichier.txt
git add fichier.txt
git status
git status
#+end_src
#+end_src
#+BEGIN_CENTER
[[file:gitlab_images/status2.png]]
[[file:gitlab_images/status2.png]]
#+END_CENTER
#+begin_src shell :results output :exports both
#+begin_src shell :results output :exports both
git commit -m "message commit"
git commit -m "message commit"
#+end_src
#+end_src
#+BEGIN_CENTER
[[file:gitlab_images/commit_git.png]]
[[file:gitlab_images/commit_git.png]]
#+END_CENTER
#+begin_src shell :results output :exports both
#+begin_src shell :results output :exports both
git status
git status
#+end_src
#+end_src
#+BEGIN_CENTER
[[file:gitlab_images/status3.png]]
[[file:gitlab_images/status3.png]]
#+END_CENTER
The file can then be transfered to GitLab:
The file can then be transfered to GitLab:
#+begin_src shell :results output :exports both
#+begin_src shell :results output :exports both
git push
git push
#+end_src
#+end_src
At this point, git will as you about your login/password unless
At this point, git will as
k
you about your login/password unless
you followed the previous /Remembering your password locally/ instructions.
you followed the previous /Remembering your password locally/ instructions.
N.B.: you will not be allowed to propagate your modifications to
N.B.: you will not be allowed to propagate your modifications to
GitLab if other modifications (e.g., from someone else) have been
GitLab if other modifications (e.g., from someone else) have been
propagated in between
propagated in between
#+BEGIN_CENTER
[[file:gitlab_images/rejected.png]]
[[file:gitlab_images/rejected.png]]
#+END_CENTER
5. Synchronizing from Gitlab: to avoid the previous problem, you need
5. Synchronizing from Gitlab: to avoid the previous problem, you need
to fetch the remote GitLab modifications first and apply them
to fetch the remote GitLab modifications first and apply them
locally.
locally.
...
...
Write
Preview
Markdown
is supported
0%
Try again
or
attach a new file
Attach a file
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Cancel
Please
register
or
sign in
to comment