fix: #814 delimiter not working for multi-value parameters#1352
Open
KamalArya wants to merge 2 commits into
Open
fix: #814 delimiter not working for multi-value parameters#1352KamalArya wants to merge 2 commits into
KamalArya wants to merge 2 commits into
Conversation
* fix: added literel newline delimitter for handling multi-value envnames * fix: Added test cases
KamalArya
requested review from
GlimmerCape,
chethana-shastry-p and
miyamuraga
as code owners
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Pull Request
Summary
When passing multiple values in multi-value parameters (such as ENV_NAMES) using the escaped newline sequence (\n), both GitHub and GitLab pipelines treat the entire value as a single literal string, rather than splitting it into separate values
Issue
Fixes #814Breaking Change?
If yes, describe the breaking change and its impact (e.g., API changes, behavior changes, or required updates for users).
Scope / Project
Specify the component, module, or project area affected by this change (e.g.,
docs,actions,workflows).Implementation Notes
Added check for "\n" while handling delimiters
Tests / Evidence
Describe how the changes were verified, including:
Additional Notes
Leave blank if not applicable.