craft your forge, build your project, grow your community freely
1---
2target: main
3status: review
4reviewers: []
5---
6 7# Want to merge startBlog
8 9To annonce the 0.2.0 release I want to explain in an article what I have done.
1011---
1213## Push 1 commit
1415### :memo: start blog with versions details
1617d79aa807609f71dff260d77c6ca482c3aa56dea2
1819- ++ [blog/version-0.1.0.md](../blog/version-0.1.0.md)
20- ++ [blog/version-0.2.0.md](../blog/version-0.2.0.md)
2122---
2324Please review changes with:
2526```shell
27git fetch origin startBlog
28git checkout startBlog
29git diff origin/HEAD..HEAD
30```3132Make your changes about the code inside the code directly (remarks, questions can be made in the form of comments). General remarks on the why can be made here. When done commit and push directly on this branch. Graft plugin will make the diff and display it here.
3334---
3536## Push 1 commit
3738### :speech_balloon: Review
39404317b6288cf46d93222d611ef7f548458554628c
4142- +- [blog/version-0.2.0.md](../blog/version-0.2.0.md)
4344```diff
45= # Version 0.2.0 is here
46=
47=
48- In this version, I focused on stabilization. I fixed over 14 bugs, some of which were known before version 0.1.0, but many of which came from you. A big thank you to everyone who participated in one way or another.
49-
50+ In this version, my main focus was on stabilisation. I fixed over 14 issues, some of which were identified before version 0.1.0, but a significant proportion were reported by you. A big thank you to everyone who participated in any way.
51+
52=
53=
54- Every time I shared gitroot, I encountered new issues with the documentation and binaries, but also questions such as "how can I compile it?" or "what's the next step?". And I'm delighted to see your enthusiasm for it.
55-
56+ Every time I shared gitroot, I came across new issues with the documentation and binaries, but also questions such as "how can I compile it?" or "what's the next step?". And I'm delighted to see your enthusiasm for it!
57+
58=
59= ## First contribution
60=
61=
62- Even though all my new contributions were related to "bug fixes", some of them required new features.
63-
64+ Although all my new contributions were related to "bug fixes", some of them required new features.
65+
66=
67= ### No notification == no contribution
68=
69=
70- The first amusing problem came from the first contributor! After 15 days, he contacted me to say, "Hi, I pushed a branch where I corrected a lot of typos, but... nothing has happened since I pushed it?". In fact, I wasn't aware of this branch. I forgot to implement a mechanism that notifies me of a new contribution!
71-
72+ The first amusing problem came from the first contributor! Fifteen days later, he contacted me to say, "Hi, I pushed a branch where I corrected a lot of typos, but... nothing has happened since I pushed it?". In fact, I wasn't actually aware that a new branch had been pushed. I had forgotten to implement a mechanism that would notify me whenever a new contribution is published!
73+
74```7576---
7778I have corrected a few typos and suggested some improvements to the phrasing.
7980Feel free to edit it again if you don't like my suggestions! 😜
8182---
8384I have cleaned this graft and commits, so the loose of commiter from you... Need to fix that in a future release.
8586I have added a paragraphe on plugin download and security.