Skip to content

Commit df7433e

Browse files
rogerkuousjvrijn
andauthored
Apply suggestions from code review
Co-authored-by: Sander van Rijn <svr003@gmail.com>
1 parent 8111a7b commit df7433e

1 file changed

Lines changed: 5 additions & 5 deletions

File tree

episodes/43-software-release.md

Lines changed: 5 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -1,5 +1,5 @@
11
---
2-
title: 4.3 Software Release and Packaging
2+
title: 4.3 Software Packaging and Release
33
teaching: 0
44
exercises: 20
55
---
@@ -90,7 +90,7 @@ Since we have not tagged any commits yet, there is unsurprisingly no output.
9090
We can create a new tag on the last commit in our `main` branch by doing:
9191

9292
```bash
93-
$ git tag -a 1.0.0 -m "Version 1.0.0"
93+
$ git tag -a 0.1.0 -m "Version 0.1.0"
9494
```
9595

9696
So we can check the tags again:
@@ -102,20 +102,20 @@ $ git tag
102102
A tag should now be listed:
103103

104104
```output
105-
1.0.0
105+
0.1.0
106106
```
107107

108108
And also, for more information:
109109

110110
```bash
111-
$ git show 1.0.0
111+
$ git show 0.1.0
112112
```
113113

114114
So now we have added a tag, we need this reflected in our Github repository.
115115
You can push this tag to your remote by doing:
116116

117117
```bash
118-
$ git push origin 1.0.0
118+
$ git push origin 0.1.0
119119
```
120120

121121
We can now use the more memorable tag to refer to this specific commit.

0 commit comments

Comments
 (0)