bates64
commented
1 year ago Perhaps we can give the frontend access to the git history at build-time for it to generate a changelog for that deployment? That is, list all squashed or merge commits since the previous deployment. Should it also maintain info for previous deploys?
Should we not generate changelogs at all, but maintain one?
Deployment Robort already sends a list of the merged PRs in the new deployment to Discord. We should surface this on the site itself, too - it doesn't necessarily have to be fancy, but we should allow for fanciness in whatever we go with (for an example of 'fancy' changelogs, see GitHub's, which they display a list of on the homepage under 'Recent Changes') We could also consider using changesets.