-
-
Notifications
You must be signed in to change notification settings - Fork 201
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[BUG] Unable to use a custom files_from_source_file_separator #1654
Comments
Thanks for reporting this issue, don't forget to star this project if you haven't already to help us reach a wider audience. |
Hi @nistalhelmuth, the separator input controls the output fields for example get all list changed files and rather than space delimited output use comma. For your use case you’ll need to specify the files_from_source_file_separator which correctly reads the files_from_source_file based on the specified separator. You can always checkout the inputs section for more information. |
Thanks for taking the time. Im sorry, I uploaded a wrong code snipped. Let me clarify: |
Hi @nistalhelmuth Can you enable debug mode as there are vital information missing in the logs section. You can copy and paste the logs or download and upload them. it’s also unclear what the bug is can you explain with examples I.e file names and what was returned. Thanks |
Actually related to this I checked the code and the separator are only used for inputs that are passed in e.g you have a comma separated list of Excerpt from the docs:
|
Is there a reason you want to read the separator in the file? |
oh! now I see. My idea was to configure comma as a custom separator for the values listed in directories_list.txt, the current behavior forced me to add an additional step to format inputs before
|
Is there an existing issue for this?
Does this issue exist in the latest version?
Describe the bug?
Is not possible to use a comma separated value file as files_from_source_file input.
To Reproduce
What OS are you seeing the problem on?
ubuntu-latest or ubuntu-22.04
Expected behavior?
Same PR just using "\n" as separator for
files_from_source_file
.Relevant log output
Has all relevant logs been included?
Anything else?
No response
Code of Conduct
The text was updated successfully, but these errors were encountered: