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
Description
When adding a new repository with a name with 29 characters the Flow When a repository is created or updated - Create an associated solution merge commit flow reports a Status Reason of Failed to link repository. Looking at the Flow run, which doesn't show as failed, the action Add new Flow fails with the message:
A validation error occurred. The length of the 'name' attribute of the 'workflow' entity exceeded the maximum allowed length of '100'..
Steps to reproduce
Steps to reproduce the behaviour:
Open 'Development Hub' App
Go to 'Repositories'
Click on 'Add'
Create a new repository with a name of length 27 characters or greater
Click 'Save'
Expected behaviour
The solution merge flow is created with a name less than or equal to 100. The repository name could be truncated or the template name could be shortened. I guess the repository name field could have a length limit but that isn't the best experience for the user just because of the Flow name. It would also be nice to have seen the flow FAILED rather that succeeded.
Environment (please complete the following information):
Description
When adding a new repository with a name with 29 characters the Flow
When a repository is created or updated - Create an associated solution merge commit flow
reports a Status Reason ofFailed to link repository
. Looking at the Flow run, which doesn't show as failed, the actionAdd new Flow
fails with the message:A validation error occurred. The length of the 'name' attribute of the 'workflow' entity exceeded the maximum allowed length of '100'.
.Steps to reproduce
Steps to reproduce the behaviour:
Expected behaviour
The solution merge flow is created with a name less than or equal to 100. The repository name could be truncated or the template name could be shortened. I guess the repository name field could have a length limit but that isn't the best experience for the user just because of the Flow name. It would also be nice to have seen the flow FAILED rather that succeeded.
Environment (please complete the following information):
The text was updated successfully, but these errors were encountered: