Feature request: dynamic prefix for commit message based on branch

Feedback Studio
1

Hello

Feature Request
I know that several GIT Versioning Systems integrate into Issue & Project tracking Software, where you can easily link and review changes made in code, directly on the issue/task/case regarding the feature/change.
Eg. Jira and Bitbucket, Gitlab etc.

This link is typically created by matching/mentioning the issue key in a commit message, which then automatically updates the issue.
In the same matter, when creating a new branch from the issue itself, the issue key carries over to the naming of this new branch.

I would love to see some kind of dynamic changing prefix for commit messages, based on the issue key (current branch selected).
I think it would make the entire development process much more fluent and complete.
Right now I have to remember to manually mention the issue key in my commit messages.

UiPath Studio:

commit prefix
commit prefix782×303 11.9 KB

Issue in Jira:

task
task1062×455 48.6 KB

Commits regarding this issue:

commits
commits1194×527 77.5 KB

Best Regards,
Soren

4

Hi Soren,

Thank you for your suggestion. I understand how this can become handy.

Is your entire work under the same Jira project, do you have multiple Jira projects, is there any naming convention you are using in naming them?

Thank you,
Alex

1 Like
7

Hello @alexandru.iordan

The feature could be for all GIT versioning systems that offers the option to create issues - Jira/Bitbucket, Github, GitLab etc.

The way we use Jira for RPA development is as follows:

  • We have one project for RPA-development
  • An ‘Epic’ in this project then represents a new RPA-project (complete solution)
  • Underlyring issues for this Epic represents development tasks to be done
  • I can then create a new branch directly from this issue, which then inherits the issue key

So in theory we could be several developers working on the same project (Epic), each working on their own specific issue (and branch).

To my understanding the same procedure is present in most other GIT Versioning systems.

Best regards
Soren

8

@SorenB excellent suggestion.

@alexandru.iordan
This feature would benefit our use case as well, although not exactly dependent on a git branch.

We use Azure Devops with self hosted agent which performs the CI/CD operations. To avoid CI and CD from triggering for each commit, our developers currently use the [skip ci] tag in each commit message.

If there was a way to append such strings by default via a config, then the developer has the choice to remove it when the CI/CD has to be triggered. In short, developers avoid writing the [skip ci] tag and only trigger it when they really want to publish a new package.

Not to forget by doing this, we can also avoid publishing packages to Dev/test or Prod orchestrators when there are minor/insignificant changes in the project.

1 Like