commit | e2a613e40518718a3931ef93279850a75fe4aa66 | [log] [tgz] |
---|---|---|
author | Louis Brunner <louis.brunner.fr@gmail.com> | Mon Sep 07 17:49:49 2020 +0100 |
committer | Louis Brunner <louis.brunner.fr@gmail.com> | Mon Sep 07 17:49:49 2020 +0100 |
tree | fd8dc4931b7b61672c1f1a058c596150b16f13e4 | |
parent | 4a05f6d092dd88b2eb5c0f984b65be4dfc0a21d0 [diff] |
Don't add a title when updating a check
checks-action
This GitHub Action allows you to create Check Runs directly from your GitHub Action workflow. While each job of a workflow already creates a Check Run, this Action allows to include annotations
, images
, actions
or any other parameters supported by the Check Runs API.
The following shows how to publish a Check Run which will have the same status as your job and contains the output of another action. This will be shown predominantly in a Pull Request or on the workflow run.
name: "build-test" on: [push] jobs: test_something: runs-on: ubuntu-latest steps: - uses: actions/checkout@v1 - uses: actions/create-outputs@v0.0.0-fake id: test - uses: LouisBrunner/checks-action@v0.1.0 if: always() with: token: ${{ secrets.GITHUB_TOKEN }} name: Test XYZ conclusion: ${{ job }} output: summary: ${{ steps.test.outputs.summary }} text_description: ${{ steps.test.outputs.description }}
See the examples workflow for more details and examples (and see the associated runs to see how it will look like).
token
Required Your GITHUB_TOKEN
name
Required The name of your check
conclusion
Optional (Required if status
is completed
, the default) The conclusion of your check, can be either success
, failure
, neutral
, cancelled
, timed_out
or action_required
status
Optional The status of your check, defaults to completed
, can be either queued
, in_progress
, completed
action_url
Optional The URL to call back to when using action_required
as a conclusion
of your check or when including actions
See Check Runs API (action_required
) or Check Runs API (actions
) for more information
Note that this will override details_url
(see next) when conclusion
is action_required
or when actions
is provided (the two inputs set the same check attribute, details_url
)
details_url
Optional A URL with more details about your check, can be an third-party website, a preview of the changes to your Github Pages, etc
Note that this will be overridden by action_url
(see previous) when conclusion
is action_required
or when actions
is provided (the two inputs set the same check attribute, details_url
)
output
Optional A JSON object (as a string) containing the output of your check, required when using annotations
or images
.
Supports the following properties:
summary
: Required, summary of your checktext_description
: Optional, a text description of your annotation (if any)See Check Runs API for more information
annotations
Optional A JSON array (as a string) containing the annotations of your check, requires output
to be included.
Supports the same properties with the same types and names as the Check Runs API
images
Optional A JSON array (as a string) containing the images of your check, requires output
to be included.
Supports the same properties with the same types and names as the Check Runs API
actions
Optional A JSON array (as a string) containing the actions of your check.
Supports the same properties with the same types and names as the Check Runs API
Note that this will override details_url
as it relies on action_url
(the two inputs set the same check attribute, details_url
)
completed
status
check even though we don't use it (see examples test_with_init*
)