vogt4nick
commented
4 years ago At first, the idea was to deploy to PyPI whenever we make a release. However, AFAICT there's no good way to trigger a Travis build when we create a release. (This makes sense, the code isn't changing, we're just adding a tag and linking a release to existing code.)
How should we handle minor changes vs patches? Not sure yet. Gotta research it.
Also, looking at existing solutions, it appears we can trigger major/minor/patch increments with commit messages. e.g.
patch: a bug fix minor: add a function major: remove a function
Is your feature request related to a problem? Please describe.
Asking people to manually keep track of the build version is fine when it's one person. It's a major pain in the ass when multiple people are developing and several PRs are open.
Describe the solution you'd like
Travis should increment the build version on every commit to master.
How should we handle minor changes vs patches? Not sure yet. Gotta research it.
Additional context
Related to #35 .