forked from github/pelican
Add AutoPub to auto-publish releases on PR merge
Contributors will henceforth be asked to include a `RELEASE.md` file containing the release type and summary of changes, which will be used by the continuous integration (CI) system to automatically publish a new release to PyPI when the pull request is merged. For more details, see: https://github.com/autopub/autopub
This commit is contained in:
parent
a7e58ac3a3
commit
06dee4de58
3 changed files with 38 additions and 0 deletions
|
|
@ -97,6 +97,14 @@ Using Git and GitHub
|
|||
For example, if you're hacking on a new feature and find a bugfix that
|
||||
doesn't *require* your new feature, **make a new distinct branch and pull
|
||||
request** for the bugfix.
|
||||
* Add a ``RELEASE.md`` file in the root of the project that contains the
|
||||
release type (major, minor, patch) and a summary of the changes that will be
|
||||
used as the release changelog entry. For example::
|
||||
|
||||
Release type: minor
|
||||
|
||||
Reload browser window upon changes to content, settings, or theme
|
||||
|
||||
* Check for unnecessary whitespace via ``git diff --check`` before committing.
|
||||
* First line of your commit message should start with present-tense verb, be 50
|
||||
characters or less, and include the relevant issue number(s) if applicable.
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue