You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
I wanted to try an alternative way to automate adding contributors. For that purpose, I wrote a GH action workflow file that is triggered whenever it detects a change in .all-contributorsrc. This runner then sets up node, generates CONTRIBUTORS.md and commits it in the same PR that triggers it. You can find the workflow file in my PR here.
However, there's a vague "There's still an error" message when running the npx all-contributors generate step. Due to the vagueness of the error message, I'm unable to diagnose what component is giving this error (could be all-contributors-cli, GHA or an error from the runner itself). It is only after knowing the source of the error, that I can try to debug it.
So I wanted to know if all-contributors-cli is throwing this error and if yes then is there a potential way to correct it?
To Reproduce
Expected behavior
Screenshots
Attaching the log message in case it gets cleaned by GH:
Additional context
Please let me know if any additional context is required.
The text was updated successfully, but these errors were encountered:
Describe the bug
I wanted to try an alternative way to automate adding contributors. For that purpose, I wrote a GH action workflow file that is triggered whenever it detects a change in
.all-contributorsrc
. This runner then sets up node, generatesCONTRIBUTORS.md
and commits it in the same PR that triggers it. You can find the workflow file in my PR here.However, there's a vague "There's still an error" message when running the
npx all-contributors generate
step. Due to the vagueness of the error message, I'm unable to diagnose what component is giving this error (could beall-contributors-cli
, GHA or an error from the runner itself). It is only after knowing the source of the error, that I can try to debug it.So I wanted to know if
all-contributors-cli
is throwing this error and if yes then is there a potential way to correct it?To Reproduce
Expected behavior
Screenshots
Attaching the log message in case it gets cleaned by GH:
Additional context
Please let me know if any additional context is required.
The text was updated successfully, but these errors were encountered: