Seems a very good idea! If you feel up to it, feel free to self-assign and work on this page!

@pi0 Work is pretty much done, if we want to leverage the ugh I will have to make a PR there to support repo/unjs/docs/pulls so we don't have to install another dep for Octokit. I will create issue and attach issue here to track 👍🏼

Thanks. If possible it would be better that we reply on default releases formating in release notes (generated during release with changelogen). They are already mapped to PRs with a reference.

@pi0 Only reason I said ungh was because it's more of interactive timeline changelog vs just a full changelog which is generated from README. Either way I can implement I think it's quite interesting seeing the pull requests and new releases on timeline vs just the log.

@pi0 what do you think?

Oh sorry i have missed this @cpreston321 do you have your branch drafted somewhere still?

@pi0 The POC I drafted above was using ungh /releases endpoint but the problem was the cache would hold too long. If new releases. I think if we wanted to leverage we would need to figure how to clear the ungh cache. If not I will have to use the changelog file but doesn't have the date meta data tied to this.

I did not unfortunately create a branch for this. I can gather your thoughts then I re-implement it.

Having a branch would be good start to play around different ideas 👍🏼 I am thinking that automd can sync back and add meta from github releases back to the CHANGELOG.md it can be most reliable source without worrying to be broken 😅

I will darft PR later today with ungh implementation then we work from there 💯

I am thinking that automd can sync back and add meta from github releases back to the CHANGELOG.md

I think that would be great :)