Implement release workflow #206
Open
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This was referenced Dec 4, 2019
Closed
|
looks good |
|
The issue is not releasing, what takes time is to review and ensure the information in the change log and the README is up to date. Thanks for the reminder. |
|
@nemesisdesign I'd recommend to cherry pick the compliance and cheanglog commit then. the changelog is for the next release and the compliance commit will force contributors to write a release note, putting load of you. |
nemesifier
force-pushed
the
master
branch
2 times, most recently
from
d137601
to
f2dc812
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This will enable automatic releases for each GitHub release that is created and will allow all djangonauts to relesae.
It will require every contributor to write a release note.
The person that releases should update to the correct version number and date.
After this is merged someone needs to set two secrets to the GitHub repo (in the settings):
TWINE_USERNAMETWINE_PASSWORD