Formed in 2009, the Archive Team (not to be confused with the archive.org Archive-It Team) is a rogue archivist collective dedicated to saving copies of rapidly dying or deleted websites for the sake of history and digital heritage. The group is 100% composed of volunteers and interested parties, and has expanded into a large amount of related projects for saving online and digital history.
Reading changelog for one package is hard #1179
Comments
|
Thanks for taking the time to send this feedback! I agree that it's not so easy to scan releases with the GitHub UI. We can easily get the list of releases by utilizing https://api.github.com/repos/slackapi/node-slack-sdk/releases This is just my two cents but building a nice web page that enables visitors to filter by modules and/or major/minor versions in https://slack.dev/node-slack-sdk/ should be useful. What do you think? > other maintainers |
|
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Description
When faced with updates from one version to the next it’s important to look at the changes between the version and as I see you are treating this with the proper care.
However, the Github UI does not help here a lot to understand the changes for one package like
@slack/web-apias there are 7 other package changelogs mixed up with the change for the package you currently care about.This is the UI one has to go through to see the changes to the packages:
It would be easier to have one list where you can see all the changes for one package.
What type of issue is this?
Requirements
The text was updated successfully, but these errors were encountered: