|
|
@@ -1,9 +1,9 @@
|
|
1
|
1
|
Is not so hard:
|
|
2
|
2
|
|
|
3
|
|
-- Easy way: use the gitea interface
|
|
4
|
|
-You will not yet get all what git is about, but you can make a new file, save it with the right name and .md extension, copy your part of the text, edit it and save it.
|
|
|
3
|
+- ***Easy way: use the gitea interface***
|
|
|
4
|
+You will not yet get all what git is about, but you can make a new file, save it with the right name and .md extension, copy your part of the text, edit it, commit it and save it. I will be notified and allow to review and push it into the repository.
|
|
5
|
5
|
|
|
6
|
|
-- use GIT
|
|
|
6
|
+- ***use GIT***
|
|
7
|
7
|
This means two things: first you will have git on your machine. Is a multiplatform software that works on terminal.
|
|
8
|
8
|
Because terminal is easy
|
|
9
|
9
|
Because terminal is the same on any machine you can enter into from remote, real or virtual.
|
|
|
@@ -38,7 +38,11 @@ then you might want to connect that repository to the public or private remote o
|
|
38
|
38
|
- When you want to register a change you ```commit``` it
|
|
39
|
39
|
- When you want to have a repository copied to your local system you ```clone``` it
|
|
40
|
40
|
- When you want to send your committed changes to the remote repository you ```push``` them, before pushing your changes you might want to ```pull``` the actual version...
|
|
41
|
|
--
|
|
|
41
|
+- Is this all? No, but is enough to start digging it. You will learn to ```clone``` ```branch``` ```push``` and ```fork``` like a pro. And everything will become clearer.
|
|
|
42
|
+
|
|
|
43
|
+Texts will be more portable, changes will be signed, errors can be passed to ```blame``` etcetera.
|
|
|
44
|
+
|
|
|
45
|
+You will never miss g-docs, ever, and everyone will love you. No, truly...
|
|
42
|
46
|
|
|
43
|
47
|
|
|
44
|
48
|
|
