More automation options for Create Release?

[cegekaJG]

I am not entirely sure if this is supported in any way with the current AL Go, so this is as much of a question as it is a feature request. Our company uses one repository per app - even if there are test apps, each repository contains a main app that should be considered first and foremost. To keep versioning simple and free from inconsistencies, I want to remove user input for every field that should follow a naming convention or has to inherit a name from a different field. I also want tags to include the version number of the app so developers can easily determine the commits used for a build and compare to make debugging more efficient. Unfortunately, since the release name and release tag both can be freely set (with the tag only having to follow semantic guidelines), developers are either forced to carefully check and copy the version number or are left with tags that only are indicative of the corresponding build when checking the release on GitHub. And since the last two numbers of the version number in the app.json manifest don't get updated with new releases, There's nothing that immediately ties a commit to a given build.

How are developers expected to use release names and tags? I don't see much reason to keep the names and tags apart, and in 99% of all cases, I'd rather just increment the tag instead of defining it from scratch and risk picking a wrong number. Additionally, if neither the manifest, commits nor the tags contain the version number of the build they produced by default, how can developers compare without having to refer to the releases on GitHub?

At the very least, it would be nice if the release name inherited the value of the tag if no name is given. Also, the tag could allow relative changes, like the version number. Ideally, I'd prefer if the release tag always matched the version number of the build of the main app used for the release, but I can see how this can cause problems.