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
-[Names and approaches used in code](#names-and-approaches-used-in-code)
17
18
-[Base project name](#base-project-name)
@@ -45,14 +46,60 @@ To generate changelog, Pull Requests or Commits must have semantic and must foll
45
46
-`feat:` for new features
46
47
-`fix:` for bug fixes
47
48
-`improvement:` for enhancements
48
-
-`docs:` for documentation and examples
49
+
-`enh:` for enhancements
50
+
-`doc:` for documentation and examples
49
51
-`refactor:` for code refactoring
50
52
-`test:` for tests
51
53
-`ci:` for CI purpose
52
54
-`chore:` for chores stuff
53
55
54
56
The `chore` prefix skipped during changelog generation. It can be used for `chore: update changelog` commit message by example.
55
57
58
+
## Updating changelog
59
+
60
+
All changes had been made before version 1.0.0 described in **CHANGELOG.previous.md** file. Starting from that version our Pull Requests or Commits have semantic and follow conventional specs above. So, we decided to keep new changes in **CHANGELOG.md** file.
61
+
62
+
**CHANGELOG.md** file should be updated after each change merged in the `main` branch. If there are several Pull Requests will be merged consistently, it's possible to update **CHANGELOG.md** once after merging all of them.
63
+
64
+
How to generate CHANGELOG automatically:
65
+
1. Merge Pull Request using `Squash`. Your commit message must follow next rule: `doc: my commit message (#1)`, where
66
+
-`doc` - type of changes (see Semantic Pull Requests)
67
+
-`my commit message` - commit message
68
+
-`(#1)` - Pull Request number
69
+
2. Rebase your local main branch on the latest changes from `main` branch
70
+
3. Run next command:
71
+
```bash
72
+
git-chglog -o CHANGELOG.md --next-tag $(semtag final -s minor -o)
73
+
```
74
+
where:
75
+
`minor` - is a type of changes related to the semver
4. Create a new branch, commit and push your changes
81
+
5. Open Pull Request using prefix `chore:`
82
+
6. Merge Pull request. Make sure your commit message looks like: `chore: Update CHANGELOG` and don't forget to clean `optional extended description`
83
+
7. Create a new Release and create the new tag (you got it when ran `$(semtag final -s minor -o)`). Click `Auto-generate release notes` and edit message leaving only commit messages:
84
+
```bash
85
+
How it was:
86
+
87
+
## What's Changed
88
+
* doc: Changelog process by @user_name in https://github.com/maddevsio/aws-eks-base/pull/#number
89
+
* chore: Update CHANGELOG by @user_name in https://github.com/maddevsio/aws-eks-base/pull/#number
This section contains the most basic recommendations for users and contributors on coding, naming, etc. The goal is consistent, standardized, readable code. Additions, suggestions and changes are welcome.
0 commit comments