Replies: 2 comments 1 reply
-
|
The message As a workaround, you may use Steps to Handle Exit Codes in GitHub Actions
3.Custom Failure Message
|
Beta Was this translation helpful? Give feedback.
-
|
🕒 Discussion Activity Reminder 🕒 This Discussion has been labeled as dormant by an automated system for having no activity in the last 60 days. Please consider one the following actions: 1️⃣ Close as Out of Date: If the topic is no longer relevant, close the Discussion as 2️⃣ Provide More Information: Share additional details or context — or let the community know if you've found a solution on your own. 3️⃣ Mark a Reply as Answer: If your question has been answered by a reply, mark the most helpful reply as the solution. Note: This dormant notification will only apply to Discussions with the Thank you for helping bring this Discussion to a resolution! 💬 |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
Why are you starting this discussion?
Question
What GitHub Actions topic or product is this about?
Actions Runner
Discussion Details
When using a shell script, the runner adds the annotation "Process completed with exit code N." for non-zero exit codes. This is redundant when a script already outputs an error using
::error::. Is there a way to suppress this other than not using a bash script?https://github.com/actions/runner/blob/0ebdf9e83d51b0ab8c168a4869954466f3e2e88f/src/Runner.Worker/Handlers/ScriptHandler.cs#L344-L348
It seems like I can use actions/github-script and core.setFailed as this does not use ScriptHandler, but ideally it'd stay as a bash script.
Beta Was this translation helpful? Give feedback.
All reactions