You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+48-36Lines changed: 48 additions & 36 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -13,11 +13,11 @@ The commands in Gitmini are intuitively named, even for users unfamiliar with Gi
13
13
## Usage
14
14
15
15
16
-
The main command in GitMini is `git publish`, which simplifies the process of publishing code changes. Use the following syntax to execute the command:
17
-
18
-
19
-
`git publish "name of ticket"`
16
+
The main command in GitMini is `git publish`, which simplifies the process of publishing code changes. Use if after working on the repo like this:
20
17
18
+
```bash
19
+
git publish "Ticket name/number"
20
+
```
21
21
22
22
When executed, the git publish command automates the following actions:
23
23
- Safely updates your local repository with `git update`
@@ -28,9 +28,9 @@ When executed, the git publish command automates the following actions:
28
28
29
29
(Soon, an option to create a merge request instead of directly pushing to the master branch will be added.)
30
30
31
-
32
-
`git unpublish "name of ticket"`
33
-
31
+
```bash
32
+
git unpublish "Ticket name/number"
33
+
```
34
34
When executed, the git publish command automates the following actions:
35
35
- Safely updates your local repository with `git update`
36
36
- Asks you to fix conflicts if they're present
@@ -44,9 +44,9 @@ Git unpublish is still under work
44
44
45
45
### Optional Commands
46
46
47
-
48
-
`git start "name of ticket"`
49
-
47
+
```bash
48
+
git start "name of ticket"
49
+
```
50
50
51
51
52
52
@@ -55,9 +55,11 @@ The git start command begins work on a new ticket. It performs the following act
55
55
- Prompts you to resolve any conflicts, if present.
56
56
- Prepare name of ticket as commit message when publishing with git publish (usefult for a future jira integration, name defaults to WIP-currentdate when no specified)
57
57
58
+
In case you forgot doing it, you can start working on a ticket after you edited some files. They will published when you git publish
58
59
59
-
`git update`
60
-
60
+
```bash
61
+
git update
62
+
```
61
63
62
64
63
65
@@ -69,9 +71,9 @@ git update is used everytime we start or publish a ticket. It automates the foll
69
71
- Applies your changes again `git stash pop`
70
72
71
73
In the future it will be possible to run update every n seconds to be always updated and receive conflicts as soon as possible.
72
-
73
-
`git current`
74
-
74
+
```bash
75
+
git current
76
+
```
75
77
Returns the name of the current ticket you're working on, in case your forgot.
76
78
77
79
@@ -87,7 +89,7 @@ That's it! You have added the aliases to your Git configuration. You can now use
0 commit comments