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
Originally posted by KristofKlein July 15, 2024
Hi,
New to the Al:Go Party :) Still playing around with it and learning a lot ( which is not as easy as I hoped for ). Anyway, a small idea: We use an external tool for Issue tracking (jira). Luckily there is integration for that in github. the only thing it needs: an issue tag in the commit message. It would be nice, If I could add that to the Al:Go workflows as an optional input that gets added to the commit message in the end as a footer.
The text was updated successfully, but these errors were encountered:
…1351)
Add support for including a suffix in the Commit message/PR message
This is useful if you have e.g. the Azure Boards integration set up in
your repository. Then you can add "AB#<WorkItemId>" to your commit/PR
messages. Currently in BCApps we require a workitem so we have to
manually edit the PRs for "Update AL-Go System Files" so it includes the
workitem. See for example: microsoft/BCApps#2455
Also related to #1352
---------
Co-authored-by: Maria Zhelezova <43066499+mazhelez@users.noreply.github.com>
Discussed in #1140
Originally posted by KristofKlein July 15, 2024
Hi,
New to the Al:Go Party :) Still playing around with it and learning a lot ( which is not as easy as I hoped for ). Anyway, a small idea: We use an external tool for Issue tracking (jira). Luckily there is integration for that in github. the only thing it needs: an issue tag in the commit message. It would be nice, If I could add that to the Al:Go workflows as an optional input that gets added to the commit message in the end as a footer.
The text was updated successfully, but these errors were encountered: