feat(report): allow slashes in version #132
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Allow the slashes in the version string to not be expaced. `feat%2Fdashboard` -> `feat/dashboard` This is better for readability as well plays nice with azure routing. For now we enforce the project name to have exactly 3 parts, for example "provider/org/name". We will need to rework that in the future to allow project names like "gitlab.com/org/team/backend/server".
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Don't enforce slashes in the version string to be espaced.
feat%2Fdashboard->feat/dashboardThis is better for readability as well plays nice with azure routing.
For now we enforce the project name to have exactly 3 parts, for example "github.com/org/name". We will need to rework that in the future to allow project names like "gitlab.com/org/team/backend/server".