search

wemake-services / kira-stale

:chipmunk: Kira's micro-bot to fight with stale GitLab issues and merge requests
MIT License
14 stars 2 forks source link

Include a gitlab-ci.yml file #20

Open bpatram opened 4 years ago

bpatram commented 4 years ago

How come we do not include a gitlab-ci.yml file in the repo? The other kira-* bots do (dependencies, release, review). Including the CI config makes it much easier to use the bot! For example, I would love to simply be able to mirror this repo in GitLab and setup the CI scheduler in Gitlab to run nightly. This is what I do for the other kira bots and it works great! Instead, I'm having to fork this repo, run the init command, commit that, and merge in any upstream changes manually.

sobolevn commented 4 years ago

@bpatram well, the reason is that we run this as a heroku service. Because it is running each 10 seconds. Which is way to frequent to be hosted on gitlab itself.

You may have a different workflow, so schedule can work for you. If this is the case, then send a PR with the file that works for you. We will use it as the example.

Thanks for sharing this! And using our stuff 🙂