Skip to content

🐿️ Kira's micro-bot to fight with stale GitLab issues and merge requests

License

Notifications You must be signed in to change notification settings

wemake-services/kira-stale

Repository files navigation

Kira Stale Bot

wemake.services kira-family Build Status Dependencies Status

Automate routine work with stale GitLab issues and merge requests.

Part of the @kira bots family.

Adding new actions

Policy:

  1. All actions must be idempotent: multiple runs – the same state
  2. All actions must make sense for all projects
  3. Dry run your script several times with --dry-run flag to make sure it works

Installation

We use gitlab-triage inside. So, consult their docs about deployment and usage.

You can even have a look at GitLab's internal policies.

It is possible to use this setup with .gitlab-ci.yml and Heroku.

Labels setup

You will need to create this set of labels:

  • deadline:soft
  • deadline:hard
  • deadline:miss
  • validation:labels
  • validation:stale
  • validation:estimate
  • validation:invalid
  • notification:first
  • notification:last

You can use kira-setup to create these labels for you.

Heroku setup

To setup a new Heroku server you will need to:

  1. Setup a scheduler
  2. Setup all env vars with tokens and ids
  3. Enjoy!

Use worker process type to run inside a scheduler every 10 minutes. Make sure to fill all env vars with the correct values.

GitLab CI setup

You can generate .gitlab-ci.yml file to run this script as scheduled events:

  1. Use --init-ci to generate default .gitlab-ci.yml file
  2. Enable scheduled builds in CI

About

🐿️ Kira's micro-bot to fight with stale GitLab issues and merge requests

Topics

Resources

License

Stars

Watchers

Forks

Releases

No releases published

Packages

No packages published

Contributors 4

  •  
  •  
  •  
  •