scrumlord

KO | EN

gitlite — search

#javascript #python #hacktoberfest #react #ai #typescript #llm #go #golang #android #machine-learning #rust #deep-learning #linux

★ 13 Open GitHub ↗

Continuous administration of the Greene Lab's electronic scrum

// repository documentation

Was this content helpful?

★ 0 (0 ratings)

# Continuous administration of the Greene Lab's electronic scrum

[![Build Status](https://travis-ci.org/greenelab/scrumlord.svg?branch=master)](https://travis-ci.org/greenelab/scrumlord)

## 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](https://github.com/greenelab/onboarding/blob/master/onboarding.md#meetings) (e-scrum) where lab members create daily task lists using GitHub issues on [`greenelab/scrum`](https://github.com/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**](https://github.com/scrum-lord).
Every day, Github Actions executes the workflow in [`scrum.yml`](./github/workflows/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](https://docs.travis-ci.com/user/cron-jobs/) 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`](LICENSE.md).

scrumlord

Explore Similar Repositories

Was this content helpful?

Recent Feedback

Download README