I've been meaning to put up an issue bot for auto labeling of issues and a merge bot for handling WIP tags etc in our company's gitlab.<p>Does anyone have experience doing the same? If so what is one thing that this bot would absolutely need to do?<p>So far I've seen them clean up stale issues, make sure contributors sign contracts. Is there something else these are good for?
I'm tracking patches for external git projects I'm using with such a local merge/rebase bot. you need to enable the rr-cache then. manual intervention only needed once a year. tracking submodules alone doesn't keep your patches.
Hey there, this is Mek from Gitlab.<p>In addition to using the bot to clean up stale issues, we are also using it for label hygiene and triage package automation.<p>- Label hygiene. Detect missed deliverable and track the version of regressions. See <a href="https://gitlab.com/gitlab-org/gitlab-ce/issues/49201" rel="nofollow">https://gitlab.com/gitlab-org/gitlab-ce/issues/49201</a> and <a href="https://gitlab.com/gitlab-org/gitlab-ce/issues/48518" rel="nofollow">https://gitlab.com/gitlab-org/gitlab-ce/issues/48518</a><p>- Triage package, we work remotely hence there is no bug grooming meeting, we do all of this in issues. A triage package is generated for each team by the bot every week. See <a href="https://gitlab.com/gitlab-org/gitlab-ce/issues/52781" rel="nofollow">https://gitlab.com/gitlab-org/gitlab-ce/issues/52781</a><p>You can set this up rather easily via the gitlab-triage project. The project is public <a href="https://gitlab.com/gitlab-org/gitlab-triage" rel="nofollow">https://gitlab.com/gitlab-org/gitlab-triage</a><p>You can see how the bot is being used in <a href="https://gitlab.com/gitlab-org/quality/triage-ops" rel="nofollow">https://gitlab.com/gitlab-org/quality/triage-ops</a>