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
{{ message }}
This repository has been archived by the owner on Jan 30, 2022. It is now read-only.
Currently the branch created is in the format "feature/<JIRA Issue #>", however if the issue is not a feature (say a hotfix, etc) that isn't reflected in the branch name as it should be. Perhaps the type of release should be either defined in the RFC ticket or as part of the CLI checkout so that branch name reflects the type of change / release being created.
The text was updated successfully, but these errors were encountered:
This makes sense; feature is not appropriate in all contexts. Ideally this would be managed in Jira; if it's type:Bug we call the branch bugfix/<Jira Issue #>?
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Currently the branch created is in the format "feature/<JIRA Issue #>", however if the issue is not a feature (say a hotfix, etc) that isn't reflected in the branch name as it should be. Perhaps the type of release should be either defined in the RFC ticket or as part of the CLI checkout so that branch name reflects the type of change / release being created.
The text was updated successfully, but these errors were encountered: