Skip to content
This repository has been archived by the owner on Jul 15, 2023. It is now read-only.

No changelog #654

Closed
emattias opened this issue Nov 15, 2018 · 2 comments · Fixed by #810
Closed

No changelog #654

emattias opened this issue Nov 15, 2018 · 2 comments · Fixed by #810
Assignees
Labels
Domain: Documentation Rules or repository tasks related to how to document code. Domain: Releases Scheduling and infrastructure around package releases.
Milestone

Comments

@emattias
Copy link

Actual behavior

No changelog listing changes in releases

Expected behavior

A changelog :)

@JoshuaKGoldberg JoshuaKGoldberg added the Domain: Documentation Rules or repository tasks related to how to document code. label Nov 15, 2018
@JoshuaKGoldberg
Copy link

JoshuaKGoldberg commented Nov 15, 2018

https://github.com/Microsoft/tslint-microsoft-contrib/wiki/Release-Notes

...but this isn't linked to on the README.md. It should be. Thanks for the issue!

@JoshuaKGoldberg JoshuaKGoldberg self-assigned this Nov 15, 2018
@IllusionMH
Copy link
Contributor

IllusionMH commented Nov 15, 2018

I believe it about releases page on GitHub.
Empty in this repo https://github.com/Microsoft/tslint-microsoft-contrib/releases
Detailed for each release in core repo https://github.com/palantir/tslint/releases

Docs: https://help.github.com/articles/creating-releases/

And I agree that it is better than wiki page and intuitive to find.

@JoshuaKGoldberg JoshuaKGoldberg added the Domain: Releases Scheduling and infrastructure around package releases. label Jan 29, 2019
@IllusionMH IllusionMH mentioned this issue Feb 3, 2019
5 tasks
@IllusionMH IllusionMH added this to the 6.1.0-beta milestone Feb 19, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Domain: Documentation Rules or repository tasks related to how to document code. Domain: Releases Scheduling and infrastructure around package releases.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants