How to specify Action "status"
See original GitHub issueThe “status” dropdown for GitHub Actions shows a lot of status codes:
But from what I can tell, the core
API only supports “success” (default) and “failure” (by way of core.setFailed()
). 1
What about all of the others though? For example, “action required”.
Presumably my action could set the process.exitCode
directly but that seems fragile for a few reasons (e.g. the status codes may change, the core
library may override this value after a task completes, etc.)
1 The README notes that core.setNeutral()
is planned but not yet supported, but that seems like it may no longer be true (https://github.com/actions/toolkit/issues/146).
Issue Analytics
- State:
- Created 2 years ago
- Comments:16 (5 by maintainers)
Top Results From Across the Web
Action Status: what it is and how to change - WeGuide
Step 1: Click on the Record Dashboard icon on the Home page · Step 2: Click on the ActionStatus for your relevant Record...
Read more >Set Action Plan Status Values - Salesforce Help
From Setup, select Object Manager. · Select Action Plan, and open Fields & Relationships. · Open Action Plan Status. · In Action Plan...
Read more >Configure case action status
Configure case action status · Navigate to All > Customer Service > Administration > Guided Setup. · On the Getting Started page of...
Read more >Action Statuses - Blackbaud
Under Actions on a constituent's record or Actions on an opportunity's record , select Settings . Choose whether to use the Completed checkbox...
Read more >Methods for tracking action status in Redux - LogRocket Blog
The usual flow goes like this: first, we dispatch the action that is supposed to set things in motion (usually the action's type...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
We have a need for the
neutral
status that isn’t really satisfied with skipping or cancelling. We would like to warn the users that their commit messages may be missing information. However, that information is optional and shouldn’t block a PR from being merged if it’s intentionally missing. A skipped or success status gives the wrong impression.Thanks @jalaziz for the feedback and additional context, I’d recommend adding your use-case and context to https://github.com/actions/runner/issues/662