Skip to content
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] Separator \n only outputs first changed file #417

Closed
3 tasks done
atorrescogollo opened this issue Mar 5, 2022 · 3 comments · Fixed by #418
Closed
3 tasks done

[BUG] Separator \n only outputs first changed file #417

atorrescogollo opened this issue Mar 5, 2022 · 3 comments · Fixed by #418
Labels
bug Something isn't working

Comments

@atorrescogollo
Copy link

Is there an existing issue for this?

  • I have searched the existing issues

Does this issue exist in the latest version?

  • I'm using the latest release

Describe the bug?

When using separator: "\n", only the first line is kept in the step output.

To Reproduce

  1. Use separator: "\n" with multiple changed files (more than one).
  2. Echo the output from the next step.
  3. In the latest step, you will only see the first changed file.

What OS are you seeing the problem on?

ubuntu-latest or ubuntu-20.04

Expected behavior?

Using separator: "\n" should set output correctly and retrieve all changed files, not only the first one.

Relevant log output

# -- STEP 1 --
> changed-files
... 
  All changed files: .terraform.lock.hcl
  testfolder with spaces/.terraform.lock.hcl
  testfolder1/.terraform.lock.hcl
  ...

# -- STEP 2 --
> echo "$CHANGED_FILES"
.terraform.lock.hcl

Anything else?

I think this can solve the problem: https://github.community/t/set-output-truncates-multiline-strings/16852/3

Code of Conduct

  • I agree to follow this project's Code of Conduct
@atorrescogollo atorrescogollo added the bug Something isn't working label Mar 5, 2022
@github-actions
Copy link
Contributor

github-actions bot commented Mar 5, 2022

Thanks for reporting this issue, don't forget to star this project to help us reach a wider audience.

@jackton1
Copy link
Member

jackton1 commented Mar 6, 2022

@atorrescogollo I’m a little skeptical about using URL encoded values to replace the separator since it would require decoding the output.

@jackton1
Copy link
Member

jackton1 commented Mar 9, 2022

@atorrescogollo This should be available in the latest release.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants