While this repo uses milestones and versioned releases, there is no easy way of tracking which issues and features made their way into a specific release, as the releases just contain the tags:
An easy way of adding that would be the maintenance of a simple markdown file listing changes in each version moving forward, and linking relevant issues or PRs. Then the section for that version could be added to the GitHub release markdown section either manually or via script.
most other repos in our tool stack do some form of this, and i do not think we can do without much longer in such a central, user-facing tool as the ARCitect.
While this repo uses milestones and versioned releases, there is no easy way of tracking which issues and features made their way into a specific release, as the releases just contain the tags:
An easy way of adding that would be the maintenance of a simple markdown file listing changes in each version moving forward, and linking relevant issues or PRs. Then the section for that version could be added to the GitHub release markdown section either manually or via script.
most other repos in our tool stack do some form of this, and i do not think we can do without much longer in such a central, user-facing tool as the ARCitect.