Skip to content

Implement "Keep-Alive" for Daniel Ridge bot so that Docker image will be updated #6266

@roslynwythe

Description

@roslynwythe

Overview

We need to implement a "Keepalive Workflow" for the Daniel Ridge bot so that it performs its function of checking the dependencies for the Docker image and when necessary, updating the Dockerfile, which triggers the process of updating our Docker hub image.

Details

Action Items

  • Clone the repository check-ghpages-versions.
  • Read and understand Daniel Ridge Bot Ops Wiki, Keep Alive Workflow and
    How To Use section of the Keep-Alive Workflow documentation
    • Note the section "Moving the keepalive workflow into its own distinct job is strongly recommended for better security" and understand the sample code
  • Incorporate the Keepalive Workflow GitHub action so that it will prevent workflows from being disabled due to inactivity in the repo
  • For testing, modify both the workflows so that they create the issue in your repository
    • .github/workflows/check-ruby-version.yml
    • .github/workflows/check-gh-pages-version.yml
  • create a PAT in your repository, then a secret called test_Daniel_Ridge_PAT and modify each workflow to use that secret in place of GH_TOKEN: ${{ secrets.Daniel_Ridge_PAT }}
  • As described in How To Use section of the Keep-Alive Workflow documentation, workflow permissions must be set. Go to repository settings, Click on Actions > General. Update the "Workflow permissions" to "Read and write permissions". Click on save.
  • On the wiki page https://github.com/hackforla/ops/wiki/@danielridgebot-Ops-Wiki, add a top-level bullet under check-gh-pages-version,yml explaning the addition of the KeepAlive Workflow action
  • Test by running .github/workflows/check-gh-pages-version.yml and verify that the appropriate issues were created
  • Restore the original secret in both workflows
  • Create a PR in https://github.com/danielridgebot/check-ghpages-versions. Put this issue in "Questions/In Review" and apply the label "ready for dev lead".

Resources/Instructions

check-gh-pages-version.yml
Keep Alive Workflow
How To Use section of the Keep-Alive Workflow documentation

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    Status

    New Issue Approval

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions