Skip to content
This repository has been archived by the owner on Mar 10, 2020. It is now read-only.

cirrus-actions/check-suite

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 

History

23 Commits
 
 
 
 
 
 
 
 
 
 

Repository files navigation

Deprecated

Since GitHub Actions were rewritten after the original version functionality of this action can be achieved out of the box by creating a workflow like this:

on:
  check_suite:
    type: ['completed']
    
name: Continue after Cirrus CI Complets Successfully
jobs:
  continue:
    name: After Cirrus CI
    if: github.event.check_suite.app.name == 'Cirrus CI' &&  github.event.check_suite.conclusion == 'success'
    runs-on: ubuntu-latest
    steps:
    - name: Continue	
      run: echo "Hello after Cirrus CI Completed"

GitHub Actions for Checks API

Build Status

To use the action simply add the following lines to your .github/main.workflow:

action "Check Suite Passes" {
  uses = "docker://cirrusactions/check-suite:latest"
  env = {
    APP_NAME = "Super App"
  }
}

This action will check that a check suite succeeded. See .github/main.workflow for a full demo workflow.

Full main.workflow example

image

Let's say a repository has Cirrus CI App installed that uses Checks API to report CI build statuses. Then your .github/main.workflow can look like this:

workflow "Cirrus CI Demo" {
  on = "check_suite"
  resolves = "Cirrus CI Passes"
}

action "Cirrus CI Passes" {
  uses = "docker://cirrusactions/check-suite:latest"
  env = {
    APP_NAME = "Cirrus CI"
  }
}

Releases

No releases published

Packages

No packages published