-
Notifications
You must be signed in to change notification settings - Fork 5
init new dev area #1
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
Conversation
This is a normal PR against the dev branch, which shows changes that are pending release
Oskar test 1 - PR process
Once some PRs have accumulated against the new dev area, we get ready for a release. |
The docs in stdprojectexample say that the merge happens on the git command line; I'm going to do it as per the docs, and then merge on the UI here if required. I'm doing things this way because that way the merge is local to my box, and if I mess something up I can reset git and get back to how things were. |
Another test against dev branch
Oskar test 2 - PR process
Add CHANGELOG.md
Add changelog comments
Fix typo in setup command
Nicely done. Regarding doing merge via commandline versus through the Github UI/PR: depending on which you do, you'll likely have to delete the inverse |
I've added @oskarpearson to bunch of projects on pypi (all except openaps), would prefer to do another few practice runs before doing that one. The basic aim here is to make master the default version, to have all tags in the master branch, to make all tags match between pypi and github, and to use dev to queue up for new releases. Well done, again. :-) |
New dev area.