Open Heet-Bhalodiya opened 3 days ago
Thanks for opening your first issue here! Be sure to follow the issue template!
Can you tell me or give me an example repo that has such issues? With the information provided, I cannot figure out what is wrong. It might be related to the configuration.
Hi @BobAnkh,
Thanks for your quick reply.
I have a few questions regarding the auto-generate-changelog
feature, and I would appreciate your guidance.
1) I have successfully used auto-generate-changelog
in a public repository. However, when I use the same workflow in a private repository, it generates an empty changelog. Is there any additional configuration required for private repositories?
2) If a single commit contains multiple messages, how does auto-generate-changelog handle and differentiate them? For example, in the image below, multiple sub-messages are present within one commit. In my public repository, the changelog only shows code refactor. How are the other sub-messages managed?
![image](https://github.com/BobAnkh/auto-generate-changelog/assets/100203834/9e93bfbb-b10e-45e8-99e1-a325b40caa06)
3) How does auto-generate-changelog
determine which messages to include in the changelog? For instance, if I have an existing changelog and want to update it after a few days to include new commits, will it consider all messages again or between the two tags or only the latest commits?
Thanks in advance.
- I have successfully used
auto-generate-changelog
in a public repository. However, when I use the same workflow in a private repository, it generates an empty changelog. Is there any additional configuration required for private repositories?- If a single commit contains multiple messages, how does auto-generate-changelog handle and differentiate them? For example, in the image below, multiple sub-messages are present within one commit. In my public repository, the changelog only shows code refactor. How are the other sub-messages managed?
- How does
auto-generate-changelog
determine which messages to include in the changelog? For instance, if I have an existing changelog and want to update it after a few days to include new commits, will it consider all messages again or between the two tags or only the latest commits?
UNRELEASED_COMMITS
to true
. In this way, the changelog will generate an ## Unreleased
part to include all unreleased commits. This configuration defaults to false
since if set to true, it will always get regeneration whenever the workflow runs (which causes a lot of requests to GitHub and might hit the rate limit).TYPE
field determines which kind of messages you want to include in the changelog. The REGENERATE_COUNT
field will determine how many recent releases it will look and regenerate the changelog. See Note 5 in README.md for more details. By default, it will only regenerate the recent 1 release to cut overhead.Contact me if you have any other questions.
Describe the bug
The workflow does not add changes to the
changelog
. Each time the workflow runs, it generates an emptychangelog
file. Even after making multiple commits (e.g., 4-5 commits) and then running the workflow, thechangelog
file remains unchanged.To Reproduce
Below is the content of my
changelog.yml
file for reference:Expected behavior
The changelog file should be updated after the workflow runs.