This is a proof of concept Ember application that:
- Uses GitHub Flow
- Requires a versioned release
- Requires a Changelog
- Developer branches
master
- Commits against branch
- Issues Pull Request
- CI builds and runs tests
- Pull Request is squashed, merged to
master
- CI builds
master
- CI updates
package.json
andCHANGELOG.md
automatically - CI pushes release to
master
- Travis is set to build
master
ember-cli-release
ultimately commits tomaster
, so the message must contain[skip ci]
- Tag must happen first so
auto-changelog
renders as expected ember-cli-release
executes the auto-changelog command- otherwise we would have two commits for every release
- 1 commit for
package.json
- 1 commit for
changelog.md
- this results in a redundant changelog entry
- changelog entries are the squash merge title