Is it possible to configure the sections created in the changelog?
See original GitHub issueHi everyone,
First of all, thank you for your work with gitmoji-changelog
. It is a very useful and interesting tool. I really like it. But I want to know if there is some way to configure the way in which it works. I want to customize the sections in which it adds the commits.
For example, I would like to have a section for Documentation
and Internationalization/localization
. These sections would be filled with the commits with:
- Documentation. 📝 (
:pencil:
) and 💡 (:bulb
). - Internationalization/localization. 🌐 (
:globe_with_meridians:
).
After read the gitmoji-changelog
I understand this should be configured in a preset, but if it is true, I admit that I don’t understand how I could configure it.
P.S. I haven’t tested it now but, gitmoji-changelog
adds a specific section for the breaking changes? I mean if there are commits with 💥 (:boom:
).
Issue Analytics
- State:
- Created 4 years ago
- Reactions:1
- Comments:5 (3 by maintainers)
Top Results From Across the Web
Form sections moved through update set do not reflect on ...
Form sections updated by navigating to sys_ui_form --> select table --> add the sections to the form and capturing them in an updated...
Read more >Add support for custom sections · Issue #316
Just came here to give big ups . Being able to group the changes per custom labels, e.g. "API" and "Front-End" would be...
Read more >Changelog entries - GitLab Documentation
This guide contains instructions for when and how to generate a changelog entry file, as well as information and history about our changelog...
Read more >To Update the Layout of a Section View Group | Civil 3D ...
Select a section view whose group layout needs to be updated. Click Section tab Modify View panel Update Group Layout
Read more >What you may not know about Forms, Form Sections, and ...
Forms should only be created by personalizing a form and creating a second form section for a view. The only reason to modify...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Awesome! You have been very fast, @frinyvonnick! 🚀 Thank you very much for the implementation of this feature.
About the questioning. I think the system should override partially the original mapping, because, at least in my case and in this moment, I am agree with the current mapping but I just want to specify some type of commits (like the examples given).
So, for example, if I want to add 🔥 (
:fire:
) to “changed”, must I rewrite both groups (changed
andremoved
)? Or, in another case, if I want to 🚀 (:rocket
) to “added”, must I rewrite all the group with the values from the default mapping if I want to keep the another values?For me it would be more useful to clarify that an emoji can be just in one category. If you know cases in which it might be in both, or there may be people interested in that, I think it should be added in the first of the two categories, but this would be like to have the emoji just in one category. Another possible solution could be to add the commit in both categories, but I don’t if it would be correct or not to have a duplicated entry in different categories. I think it wouldn’t be agree with conventional changelogs.
Again, thank you for your work!
P.S. Really awesome to see you working on gitmoji-changelog!
Hi @ivanhercaz, thank you for posting this feature request 🙏
I made an implementation proposal in PR #155.
How it works:
You need to create a
.gitmoji-changelogrc
in your project folder with the following content:It will now only handle these two categories with commits using
pencil
,bulb
andglobe_with_meridians
.You will need to start from the actual mapping to cover all kind of commits.
Questionning
I’m asking myself if the system should override totally or partially the original mapping. So users can just add new categories without having the whole mapping in his configuration file. What are your thoughts about it @ivanhercaz @bpetetot?
In this case if a emoji has already a category in the default mapping you will have to override this category too so you can remove this emoji from it. In case an emoji is present in two categories what should we do?