Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Use Git/Github releases instead of giant README #138

Open
Anahkiasen opened this issue Apr 13, 2016 · 3 comments
Open

Use Git/Github releases instead of giant README #138

Anahkiasen opened this issue Apr 13, 2016 · 3 comments

Comments

@Anahkiasen
Copy link
Contributor

Currently new releases are rolled out through an ever-changing README. For notifications and management purposes it might be a better idea to use Git releases for that purpose.

Using a date-based version system in your case, a simple git tag 20160101 would work, and then in each release you can specify the changelog on Github. For those of us that watch the repo it would allow us to get notifications when new releases are available and know that we need to refresh the bookmarklet.

@genbtc
Copy link
Collaborator

genbtc commented Oct 24, 2016

Wow. I finally started this. https://github.com/zininzinin/AutoTrimps/releases I really wish I had taken your suggestion earlier. Can you please help me find my way with the new system ? I like that now we can refer the script to URLs with the version number in it, (in case i break something you can target the last stable release's URL).
About the README, I feel like these new releases/tags should be itemized on the README (since it's the front page new people see), is there a way we can add Releases's hyperlinks automatically ? OR do you have any repos to point me to that do this efficiently that i can model mine after? Or anything else.

@Anahkiasen
Copy link
Contributor Author

Anahkiasen commented Oct 24, 2016

Standard is usually to have a separate CHANGELOG.md file containing the release notes, with the header of each version pointing to the Github release (or a diff between that version and the last, depending on what you prefer). But in your case that could be done in the README.md itself. Although you would still need to copy/paste the release notes between your README and the Github release.

That being said the most important part is the Git tag, the Github release doesn't have to contain the release notes if they're already in the README, so you could pretty much have your changelog in your README like right now, just, with a link to each github release on each version.

More information on the KAC standard to write changelogs http://keepachangelog.com/en/0.3.0/

@Anahkiasen
Copy link
Contributor Author

Also as a note you can tag Git commits retroactively, so you could still tag old releases if you wish so

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants