Skip to content
This repository has been archived by the owner on Aug 21, 2022. It is now read-only.

A Github action to keep Another repo workflow alive

License

Notifications You must be signed in to change notification settings

MHG-LAB/Workflow-Keep-Alive-Test

 
 

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 

History

24 Commits
 
 
 
 
 
 

Repository files navigation

Workflow-Keep-Alive

Run

A Github action to keep Another Repo workflow alive after 60days inactive

Steps:

  1. Fork this repository
  2. Create some sercets in your repository(Settings -> Secrets)
    • REST_TOKEN: Create a token with the permission admin:org, delete:packages, repo, user, workflow, write:packages in the access token, and then use the value of this token to create a sercet named REST_TOKEN in your repo
    • API_ADDRESS: Use this format: https://api.github.com/repos/{owner}/{repo}/actions/workflows/{workflow_id}/enable
      You can replace workflow_id with the workflow file name. For example, you could use main.yaml
      See Docs in https://docs.github.com/cn/rest/reference/actions#enable-a-workflow
  3. Run github action again,check if the workflow in another repo is enabled.

Notice: This workflow could be disabled by Github after 60 Days inactive. To wake up mutually,YOU MUST Do above steps in the target repo's workflow again,then add following Github Action after step:

    - name: curl
      id: enable_workflow
      env:
        REST_TOKEN: ${{ secrets.REST_TOKEN }}
        API_ADDRESS: ${{ secrets.API_ADDRESS }}
      run: |
        echo "Enable Workflow Start..."
        curl -X PUT -H "Authorization: token $REST_TOKEN" "$API_ADDRESS"
        echo "Finished"

And cron timer after on:

schedule:
    - cron: 00 00 * * *

Run github action and check if this repo workflow is enabled.

About

A Github action to keep Another repo workflow alive

Resources

License

Stars

Watchers

Forks

Releases

No releases published

Packages

No packages published