Hi, Thank you very much for the great content. I've been using half conventional commits but without any linting and with emojis and it kinda created some inconsistency in my commit messages. With your explanations it's so much better and I'll make sure to install these tools to help me have better commit messages.
Hi, no need to apologize. It's the BPHS1 from audio-technica www.audio-technica.com/en-eu/bphs1 Please be aware that this is a professional broadcast microphone and as such it's connection is NOT usb. It's XLR so you need a so called audio interface (it's like an external audio card) to connect it to your conputer. Btw I have 2 videos that you might like ruclips.net/video/qxu895PSYXA/видео.html and ruclips.net/video/1yfh04TtVGk/видео.html I hope it helps. Cheers and happy coding!
So how is this actually used in a repo? For instance, if I created a new feature with tests and I update the documentation to document the new feature... would that be a feat, test, or doc type commit or 3 separate commits? If it's 3 separate commits, wouldn't that break the idea that each commit is in a complete state? Is this where branching comes into play? Or?... would have been great to see an actual workflow using this convention.
Your intuition is correct. It's 3 separate commits. In fact it's one of the goals to force you to do only one thing in a commit instead of accumulating potentially unrelated changes. This makes PR reviews much more pleasant and likely to happen in the first place. The "each commit in a complete state" thing depends on the definition of complete I guess. Whatever it means I doubt that anyone would argue that an entire feature needs to be squashed into 1 commit. I wouldn't want to review a PR like this.
How to make conventional git commits if we don't use any lint and node let's I have php project with git now how to do conventional git commits by not using any lint etc. Just use the terminal ?
What do you mean? It's just a convention for commit messages. If there are no tools to support you, you write the commit messages yourself. I'm using the node setup in Scala projects all the time.
@@DevInsideYou actually I am new to this, so according to your response I assume that we cannot make these conventional commits without any tools like not only with help of terminal If there is some way to create via terminal only, then can you please refer me some docs, site, or your video etc, please ? I know that we can add only git commit -m title -m description But how to add footer here and how to make it like conventional commits ?
If you just do "git commit" without any parameters your default editor will open and this way you can have a multi-line commit message. Leave the second line empty and put the footer starting from the third line.
Yeah I don't remember what happened but the entire playlist ended up having a very low volume. The good news is that those videos are a couple of years old by now. My recent videos are loud enough.
Table of Contents:
00:00 intro
00:35 semantic versioning (semver)
05:22 overview
06:14 Git commit message guidelines
06:58 conventional commits
13:29 commit litner: commitlint
16:59 commit generator: commitizen (cz)
19:42 replace topics with emojis (cz-emoji)
Красота! Спасибо за отличную инструкцию!
Hi,
Thank you very much for the great content. I've been using half conventional commits but without any linting and with emojis and it kinda created some inconsistency in my commit messages.
With your explanations it's so much better and I'll make sure to install these tools to help me have better commit messages.
Hi, sorry for the question but You sound very well and may I ask You what is your headphones model? :)
Hi, no need to apologize. It's the BPHS1 from audio-technica www.audio-technica.com/en-eu/bphs1 Please be aware that this is a professional broadcast microphone and as such it's connection is NOT usb. It's XLR so you need a so called audio interface (it's like an external audio card) to connect it to your conputer. Btw I have 2 videos that you might like ruclips.net/video/qxu895PSYXA/видео.html and ruclips.net/video/1yfh04TtVGk/видео.html I hope it helps. Cheers and happy coding!
@@DevInsideYou thank You :) i will watch Your other video for sure :) it is a pleasure
verrrry helpful thank you
So how is this actually used in a repo? For instance, if I created a new feature with tests and I update the documentation to document the new feature... would that be a feat, test, or doc type commit or 3 separate commits? If it's 3 separate commits, wouldn't that break the idea that each commit is in a complete state? Is this where branching comes into play? Or?... would have been great to see an actual workflow using this convention.
Your intuition is correct. It's 3 separate commits. In fact it's one of the goals to force you to do only one thing in a commit instead of accumulating potentially unrelated changes. This makes PR reviews much more pleasant and likely to happen in the first place.
The "each commit in a complete state" thing depends on the definition of complete I guess. Whatever it means I doubt that anyone would argue that an entire feature needs to be squashed into 1 commit. I wouldn't want to review a PR like this.
How to make conventional git commits if we don't use any lint and node let's I have php project with git now how to do conventional git commits by not using any lint etc. Just use the terminal ?
What do you mean? It's just a convention for commit messages. If there are no tools to support you, you write the commit messages yourself. I'm using the node setup in Scala projects all the time.
@@DevInsideYou actually I am new to this, so according to your response I assume that we cannot make these conventional commits without any tools like not only with help of terminal
If there is some way to create via terminal only, then can you please refer me some docs, site, or your video etc, please ?
I know that we can add only
git commit -m title -m description
But how to add footer here and how to make it like conventional commits ?
If you just do "git commit" without any parameters your default editor will open and this way you can have a multi-line commit message. Leave the second line empty and put the footer starting from the third line.
you are using a microphone very near to your mouth, but still the volume is extremely low.
Yeah I don't remember what happened but the entire playlist ended up having a very low volume. The good news is that those videos are a couple of years old by now. My recent videos are loud enough.