citeproc-py
citeproc-py copied to clipboard
brechtm
Release automation
Windows ppl (like @rly are waiting for it)
should we wait for #120 or cut it before?
you ( @brechtm ) or me or someone else?
interested to auto it? We use it in increasing number of projects, see e.g. https://github.com/dandi/dandi-cli/ with its https://github.com/dandi/dandi-cli/blob/master/CHANGELOG.md produced by auto from PR titles and labels.
#120 is only relevant to development, so don't let this delay a release.
As always, I'm quite busy with other projects, so it would be great if you could make a release. Don't feel obliged, though!
ok, 0.6.0 released. Not sure why tarball did have generated .rng before and then not -- added .rng explicitly in MANIFEST.in . Tested via duecredit on windows -- seems to install and work. So the question remains: would you mind if we automate releasing? I hate doing it manually these days.
Ah, I didn't know what auto was. Looks neat! It seems a bit over the top at first glance. But I agree that having to manually create releases is a pain and holding back releases. So, go for it, if you feel up to configuring it!
Seems I'll just have to remember to never commit to master directly, but use PRs instead. Can pushes to master be disabled?
I believe so. In the branches section of the Settings for the repo you can configure branches protection.
https://stackoverflow.com/questions/46146491/prevent-pushing-to-master-on-github#:~:text=To%20find%20it%20go%20to,people%20who%20are%20not%20moderators.
@jwodder - isn't it a good idea for any repo using auto for releases? or an overkill?
@yarikoptic Any commits made directly to master are displayed by auto in their own section, as seen here. Whether that's desirable or not is up to you.
Note that, if branch protection is enabled, auto will need to be supplied with a personal admin token in order to push CHANGELOG commits to master, as described here.
