-
-
Notifications
You must be signed in to change notification settings - Fork 849
What Tags to use to create Headings in Changelog #495
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
Labels, @hendrikeng. GitHub Labels. I'll add one now, to this GitHub Issue. Each repo has a page like this: https://github.com/skywinder/github-changelog-generator/labels Administrators of that project can define new labels there. They're the ones that are used by this tool, to categorize Issues/PRs. Does this answer your question? |
ah ok...i guess i misunderstood the whole concept then. So if i, in example, start a new project, i would create all features and functions i want to program as issues before i start. e.g. button xyz: when its finished, commit it with feature #1 button and it would be stated in my changelog as feature implemented etc .... does that makes sense ? thanks a lot for your explanation |
Dark secret: each GitHub Pull Request is an Issue (just with some more metadata on it, and displayed differently on the github.com website). Pull Requests are also sorted in under their (label) heading. |
Thanks a lot @olleolleolle :-) |
Have a great weekend. |
Hey there, thanks for the awesome generator, it all works i just couldn't figure out wich tags to use in commit messages to create the headings like :
only closed issues was automatically generated in the changelog, i tried add: , fixes: etc...what am i missing..thanks a lot
The text was updated successfully, but these errors were encountered: