Comments (5)
Fixed 😂
from github-changelog-generator.
Related: #18
I also have that opinion.
from github-changelog-generator.
Related: #101
Is that a recursion joke? 😆
from github-changelog-generator.
we should add each commit since the last release, which might or not be associated to a PR.
This has the advantage of also making this module work even if one commited directly to master innocent.
For what my opinion's worth, I tend to agree with the common recommendation that all changes to a collaborative repository should happen via pull requests, as that improves visibility of the changes, allows them to be reviewed, and offers consistency between simple changes that only require a single commit and those that would be better split into multiple related (but independent) commits.
In fact, the good practice of atomic commits would precisely lead to commit messages that aren't necessarily a good fit for a changelog, since the latter should focus on whole features / functional changes / user stories, rather than the steps required to achieve them.
If anything, I would prefer seeing mechanisms in place to prevent commits made without PRs.
from github-changelog-generator.
@satazor since GitHub says that you closed this as "completed", could you confirm whether that is the case? I.e. did you make changes to this repo to enable commit-based changelogs, or did you simply use GitHub's default closing reason?
from github-changelog-generator.
Related Issues (20)
- Changelog generation fails when there're no releases
- Query tags instead of releases HOT 3
- Create GitHub release per changelog entry HOT 1
- Remove tag 0.1.0 HOT 1
- Filter PRs by base.ref = master HOT 1
- Add merger username to each PR entry
- Consider grouping PRs into categories HOT 1
- Publish package to npm's @uphold namespace HOT 1
- Changelog is generated with empty release names HOT 3
- Remove unnecessary content by filtering with .npmignore HOT 1
- Update project description on package.json
- Sort package.json
- Filter master merges when generating the CHANGELOG HOT 1
- Build changelog on top of existing one HOT 1
- Preserve upstream changelog
- Use conditional requests to improve performance
- Filter the list of pull requests by a specific label
- Upgrade `@octokit/rest` to version `>16` HOT 1
- Don't include unreleased changes
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from github-changelog-generator.