Skip to content

Latest commit

 

History

History
44 lines (32 loc) · 2.63 KB

README.md

File metadata and controls

44 lines (32 loc) · 2.63 KB
Raw

Continuous administration of the Greene Lab's electronic scrum

Build Status

Summary

This repository automates the management of GitHub issues, which must be opened and closed based on the date.

Details

The Greene Lab does an electronic scrum (e-scrum) where lab members create daily task lists using GitHub issues on greenelab/scrum (private repository). To automate the administration of greenelab/scrum issues, this repository relies on Github Actions daily cron jobs and a GitHub machine user named @scrum-lord. Every day, Github Actions executes the workflow in scrum.yml. As appropriate, @scrum-lord closes and opens issues to keep the scrum issues up to date.

Github Actions Deployment Instructions

  1. Fork repo
  2. Create new empty repo organization/scrum
  3. Get Github login token (https://help.github.com/articles/creating-a-personal-access-token-for-the-command-line/) with repo and workflow scope
    • The safest way to do this is to create a new machine user that doesn't have any other privileges than for the scrum repo
  4. In the settings for the workflow repo:
    • Create environment variable named SCRUMLORD_TOKEN whose value is the login token from step 3.
  5. Commit changes to master branch to fit your settings (see https://github.com/gentnerlab/scrumlord/network for examples)

Travis-ci Deployment Instructions

Use these instructions to deploy a new instance of the scrumlord in travis-ci to manage scrum issues for a repository

  1. Fork repo
  2. Create new empty repo organization/scrum
  3. Get Github login token (https://help.github.com/articles/creating-a-personal-access-token-for-the-command-line/) with repo scope
    • The safest way to do this is to create a new machine user that doesn't have any other privileges than for the scrum repo
  4. log into https://travis-ci.com using github
  5. Add new repo to travis-ci: organization/scrumlord
  6. In the settings for that travis-ci repo:
    • Add daily cronjob to always run master branch
    • Create environment variable named GH_TOKEN whose value is the login token from step 3.
  7. Commit changes to master branch to fit your settings (see https://github.com/gentnerlab/scrumlord/network for examples)

Reuse

Anyone is welcome to adapt this codebase for their use cases. The repository is openly licensed as per LICENSE.md.