Update gitstream.cm #25
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
In this version:
We're still using a custom expression called branch_prefix.
The expression now uses branch.find('/') to locate the first slash.
If a slash is found, it takes everything before it. If not, it uses the whole branch name.
This approach avoids using the split() function, which might be causing issues.
Testing gitStream functions to validate capabilities in order to rebuild branch labeling function
This configuration does the following: It still always runs (condition is true). It adds a label that includes the word "branch-" followed by the full branch name. This step introduces the use of the branch variable within a Jinja2 expression, but doesn't yet attempt to manipulate the branch name.
This configuration does the following: It still always runs (condition is true). It uses the split filter to divide the branch name at the '/' character. It then uses the first filter to select the first part of the split result. This should add a label that's just the first part of the branch name (e.g., "feature" for a branch named "feature/new-login").
In this configuration: We've moved the string manipulation logic to a custom expression called branch_prefix. The custom expression uses Python-like indexing ([0]) to get the first element after splitting. We've added a conditional to handle cases where there's no '/' in the branch name. In the automation, we simply reference the custom expression.
This configuration does the following: It uses the branch_prefix custom expression we developed to add a label based on the first part of the branch name. It introduces a new custom expression is_hotfix to check if the branch name starts with "hotfix/". It adds a second add-label action that will add an "urgent" label if is_hotfix is true.
Update gitstream.cm
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.
In this version:
We're still using a custom expression called branch_prefix. The expression now uses branch.find('/') to locate the first slash. If a slash is found, it takes everything before it. If not, it uses the whole branch name.
This approach avoids using the split() function, which might be causing issues.