Link to "What changed since the previous release?"
See original GitHub issueExample: https://github.com/parcel-bundler/parcel/releases
Can you tell what each release includes? GitHub links to the tagged commit but that’s rather useless
Wouldn’t it make sense to list the commits between each tag/release (in chronological order).
This is the link that should appear on v1.4.1
: https://github.com/parcel-bundler/parcel/compare/v1.4.0...v1.4.1
Without any fetches we can show the link on
- lists but not each tag/release pages
- every tag in a list, except the last one
hardikmodha earned $80.00 by resolving this issue!
- Checkout the Issuehunt explorer to discover more funded issues.
- Need some help from other developers? Add your repositories on Issuehunt to raise funds.
Issue Analytics
- State:
- Created 6 years ago
- Reactions:14
- Comments:25 (23 by maintainers)
Top Results From Across the Web
Find what's changed in a file - Google Docs Editors Help
You can see changes that have been made to a document in Google Docs, Sheets, ... To return to the original current version,...
Read more >Committing a change on a previous release version on master
Once it's ready to ship, the release branch gets merged into master and tagged with a version number. The point is: even if...
Read more >Keep a Changelog
Version 1.0.0 # Changelog All notable changes to this project will be documented in this file. ... Links to latest released version in...
Read more >Linking to releases - GitHub Docs
On GitHub.com, navigate to the main page of the repository. To the right of the list of files, click Releases. Releases section in...
Read more >View the version history of an item or file in a list or library
The choices change based on whether you selected the latest file, or an earlier version. The version history window for the most recent...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Ok, then only fetch that page: https://github.com/parcel-bundler/parcel/releases?after=parcel-bundler@1.12.3
@parcel/integration-tests@***
), only look in that page. If none are found, ignore the tag or just use the previous non-prefix-aware tagIf we really want to add a
Next
link we need to find a solution that does not require multiple consecutive fetches (whether it’s the pagination link or the brute force). But for now we can ignore itOne thing to keep in mind is, as seen on the
parcel
repo, they have multiple tags on the same commit, so “the previous tag” is not necessarily “the one below it”.If not too complex (and if this is a standard many repos follow), there could be smart specific links like
parcel-bundler@1.12.2...parcel-bundler@1.12.3
onparcel-bundler
tags@parcel/integration-tests@1.12.2...@parcel/integration-tests@1.12.3
on@parcel/integration-tests
tagsIf too complex, it should at least make sure “the previous tag” doesn’t point to the same commit. e.g.
parcel-bundler@1.12.3...@parcel/integration-tests@1.12.3
(both are on09c1082
)