You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We currently have release notes under our releases page, which is great for the average user. But technical users are also interested in the source changes, which we don't cover well at the moment. We should start including a commit range in every release. We can backfill existing releases.
Normally such stuff would live in a CHANGELOG. But I'm hesitant to add a CHANGELOG in addition to the Releases because it creates more process by having to put release notes in two places. If we do decide to have a CHANGELOG, one option is to keep it empty and have it link to the Releases.
The text was updated successfully, but these errors were encountered:
Started updating Releases using a comparison between tags such as https://github.com/dideler/toggle-youtube-comments/compare/<old-tag>...<new-tag>
Have to head out for a bit, still have a few more to go before we can close this ticket.
We currently have release notes under our releases page, which is great for the average user. But technical users are also interested in the source changes, which we don't cover well at the moment. We should start including a commit range in every release. We can backfill existing releases.
Normally such stuff would live in a CHANGELOG. But I'm hesitant to add a CHANGELOG in addition to the Releases because it creates more process by having to put release notes in two places. If we do decide to have a CHANGELOG, one option is to keep it empty and have it link to the Releases.
The text was updated successfully, but these errors were encountered: