The footer should contain any information about Breaking Changes and is also the place to reference Issues that this commit refers to.

Conventionalmeaning in Hindi

@julian-alarcon IMHO ci commit are typically changes to something related to build the software/artifact or something related to test the software or something related to changes in the behaviour of the process of the deployment (operational task) therefore ops

If I make a change in this configuration file, what would you put for the type? refactor?(since it is part of source code..?)

Conventionalsynonym

@Borodkov you can not use \d in bash regex use [[:digit:]] instead e.g. (^(#[[:digit:]]{1,3} )(feat|fix|refactor|style|test|docs|build): .+$)

Conventionalmeaning andexamples

can you help me with server side script? on my home Gitlab @ ubuntu 20.04 LTS create pre-commit hook in repository but got error on push from client: pre-receive: 32: Syntax error: "(" unexpected (expecting "then")

The build type is usually reserved for changes that affect the build system, such as updating dependencies, configuration files for build tools, or scripts that are essential for the build process. Since the initial commit is more about setting up the project structure and doesn't specifically involve modifying or adding build-related configurations, using chore is more fitting for this purpose. @andre-alck

@nikitarevenco I think it make sense in your scenario as well. In you use-case adding new content is a new feature because it will add a new feature to the primariy interface in this case the interface is a document. However I guess docs commits will be quite rare, because docs commit basically will add description on how to iteract with the project interface in your case a document, but maybe there will be some cases.

Have a look at git-conventional-commits , a CLI util to ensure these conventions, determine version and generate changelogs

Conventionalmeaning

A: fix: update syntax error in ci config B: build: fix syntax error in ci config C: fix(ci): update syntax error in ci config

Should be feat because it will effect the API. Take feature as a synonym of behavior. When ever a behavior is changed by purpose it is most likely a feat commit if you repair an exit behavior it is most likely a fix commit.

Conventional examplesin real life

Should be feat because it will effect the API. Take feature as a synonym of behavior. Wen ever a behavior is changed by purpose it is most likely a feat commit if you repair an exit behavior it is most likely a fix commit.

Next, when comment lines 32 and 37 (if condition) if ! [[ "$commit_msg_header" =~..... ... fi got 3 echo of my commit hash, "ERROR: Invalid commit message format", commit msg body

Unconventionalexamples

@doni404 In the end it depends on what your first commit contains. If it is just a README it is probably docs if you have a hello world program with build process build make sense, if it already contains a real feature it might be an feat commit. If you just commit an .gitignore file or even create an empty commit chore: init would be appropriate.

Conventionalmeaning in Urdu

The first commit is tricky, I think build is probably the best choice, however I'd tend to always use just init as the very first commit. Ill add this recommendation to this gist.

Nice posting! I have a question. What whould you put for changes for framework configuration files? For springboot application (not sure you are familiar with springboot tho), it has a application.yaml file that keeps some configurations like below.

Examplesofconventionalwords

What about commits in repositories that aren't even code? For example text-only .md repos. I usually do something like this myself:

Hey. What type would I use, if I had some method, and I would only change some value in it, that would change the behavior of the program, but would not add or remove any feature.

What about adding ci ? As recommended here: https://www.conventionalcommits.org/en/v1.0.0/ to describe changes related with CI/CD pipelines?

Finally! A clear, simple and concise explanation of the Conventional Commits format! So much better than the documentation on the actual website!

A great example can be a method validate_registration(person), that would check for person age for example. In this example, how could I name the commit changing the minimum age from 18 to 15 years?