Hackaton for release toolkit#205
Open
kilokang wants to merge 5 commits into
Open
Conversation
kilokang
force-pushed
the
kang-makes/hackaton-release-toolkit
branch
2 times, most recently
from
d228670 to
4a60b04
Compare
kilokang
force-pushed
the
kang-makes/hackaton-release-toolkit
branch
from
4a60b04 to
50baef8
Compare
kilokang
force-pushed
the
kang-makes/hackaton-release-toolkit
branch
from
68ff335 to
6999470
Compare
kilokang
force-pushed
the
kang-makes/hackaton-release-toolkit
branch
3 times, most recently
from
7daf90e to
99bd697
Compare
kilokang
force-pushed
the
kang-makes/hackaton-release-toolkit
branch
from
99bd697 to
97bff5b
Compare
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
I am trying to solve as many issues the release toolkit has open.
Opening many PRs will make all changes a hell of PRs so I will concentrate all of them in the same PR keeping a good history of commit so following the changes is easier.
To review this PR, go commit by commit. I added the change I wanted to make in that commit in the
CHANGELOG.mdfile so reviewer can follow the changes and release notes are created properly for all these changes.Solves #114