Skip to content
This repository has been archived by the owner on Nov 6, 2020. It is now read-only.

Add a Changelog file to the repo to enable native Changelog view in VS Code #183

Closed
lumaxis opened this issue Apr 20, 2017 · 6 comments
Closed

Comments

@lumaxis
Copy link

lumaxis commented Apr 20, 2017

VS Code powers it's integrated Changelog view based on a CHANGELOG.md file, placed at the root of the project's folder. See https://code.visualstudio.com/docs/extensions/publish-extension#_marketplace-integration for details.

screenshot 2017-04-20 23 11 14

It would be great to add this to allow people to see what changed in a new version of this extension right from VS Code! 👍

@jeffyoung
Copy link
Contributor

Good idea @lumaxis.

Maybe something generated with a tool like github-changelog-generator. Although it'd be great if it was something I could put right into my gulp build (via npm).

@lumaxis
Copy link
Author

lumaxis commented Apr 21, 2017

@jeffyoung How do you currently create the GitHub releases? Maybe working the other way around and auto-creating those from a Changelog file would be an easier solution. Maybe using something like https://github.com/MoOx/github-release-from-changelog?

@jeffyoung
Copy link
Contributor

I currently do it manually. I keep track of the "Release Notes" myself (since I don't want all of the commits showing up there (or in a CHANGELOG file)) and once I get the VSIX file ready to upload to the marketplace, I create the release in GitHub. Since I have the vsix file ready, I can just drag-and-drop it right into the Release so it's available there (mostly for historical purposes).

jeffyoung pushed a commit that referenced this issue Apr 24, 2017
@jeffyoung
Copy link
Contributor

I went ahead and created this (although I'll have to do it manually for now). Thanks for the suggestion @lumaxis.

@lumaxis
Copy link
Author

lumaxis commented Apr 24, 2017

Thank you 🙏

@lumaxis
Copy link
Author

lumaxis commented Apr 24, 2017

It's beautiful! 🙂

screenshot 2017-04-24 23 33 40

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

No branches or pull requests

2 participants