Open ross-spencer opened 1 year ago
Hi, can you post a link to the action run that shows that error?
@EndBug this is one example: https://github.com/ross-spencer/tmp/actions/runs/4708941556/jobs/8351695598
Thanks for reporting that, I'll try to look into it as soon as I have some time ;)
@ross-spencer did you ever end up resolving? We have a similar issue going on in our workflow, wondering if you were able to debug at all.
@andrewwylde not that I recall, I think I just used a different approach, I'd need to go back and look at the workflow.
Did this ever end up resolved? I just get a bunch of javascript code when I try to use it.
@Luiggi33 we went with a manual approach to resolving this (just using git
). Code here.
It worked for our workflow, but may not for others.
Hope that helps!
Thanks for the reply, we ended up using some other action that suited our needs
I know this is an old issue, but for anyone it may help: The issue seems to be occurring when you include the the cwd
input & point it to an absolute path.
For example, the following code will fail with the exception as the error:
- name: Pushing Calver File
uses: EndBug/add-and-commit@v9
with:
cwd: "${{ github.workspace }}/my-checkout-path"
add: "version.txt"
pathspec_error_handling: exitImmediately
author_name: "github-actions[bot]"
author_email: "41898282+github-actions[bot]@users.noreply.github.com"
committer_name: "github-actions[bot]"
committer_email: "41898282+github-actions[bot]@users.noreply.github.com"
message: "Workflow run [#'${{ github.run_number }}']: Bumping calver"
pull: '--ff'
However, if I modify the cwd: "./my-checkout-path"
to not use an absolute path, the step completes successfully.
Describe the bug A clear and concise description of what the bug is. If a particular error is shown
Currently seeing this output in GH actions when giving this a try:
NB. Truncated...
Workflow used Provide a snippet of the workflow and/or a link to it (use the commit sha as the ref when you link it, so that it's not influenced by other changes). If you only share a section of the workflow, make sure it includes the step that uses the action!
Expected behavior A clear and concise description of what you expected to happen.
I'm not sure at this point. Some sort of initialization and then a clear message if that fails.
Logs Either provide a link to the action run or (if your repo is private) paste here the logs from the step that uses it. If you paste the logs, please use this template, and remember to paste the logs from all the different sections.
As above.