Adding a contributing and maintenance guide.#149
Conversation
This is just a starting point. I'm sure we can keep on improving it. Personally for me, I just needed to have the "how to release" written up since I keep forgetting how to do it.
Codecov Report
@@ Coverage Diff @@
## master #149 +/- ##
=========================================
Coverage 100.00% 100.00%
=========================================
Files 8 8
Lines 405 405
Branches 74 74
=========================================
Hits 405 405 Continue to review full report at Codecov.
|
| - Create a new branch for the release. | ||
|
|
||
| - Push the "release" branch to remote. | ||
|
|
There was a problem hiding this comment.
I actually never do this. 😄 What I do is I start a branch locally with what I think the final state will be, run the tests, do the build, upload, commit my changes, and then create a GH release (so it creates the git tag).
There was a problem hiding this comment.
Do you use GitHub CLI to release then? I have only been using the web UI, and I needed to either push the branch or the tag in order to do it from the web.
There was a problem hiding this comment.
Nope, web UI. The Releases page will create a new tag from the point that any branch is currently at if the name doesn't already exist.
brettcannon
left a comment
brettcannon
left a comment
There was a problem hiding this comment.
LGTM, although I follow a different approach when doing the final changes for the release.
2 participants
This is just a starting point. I'm sure we can keep on improving it.
Personally for me, I just needed to have the "how to release" written up
since I keep forgetting how to do it.