Use alpine-qa-bot in postmarketOS

added ci label

comment / close stale issues too (all postmarketOS git repositories)

This is done via the AutoStale poller job, just add the project IDs in the PollerIDs section of the configuration, it will try to get the configuration for the specific repository in .gitlab/aports-qa-bot.json, see this example from alpine/aports

{
    "NotStaleLabels": ["status:mr-hold"],
    "StaleDays": 30,
    "StaleLabel": "status:mr-stale",
    "StaleMessage": "Sorry to bother you @%s,\n\nbut we've detected that this merge request hasn't seen any recent activity. If you need help or want to discuss your approach with developers you can ping `@%s`. You can also ask on IRC on `#alpine-devel` on irc.oftc.net. If no further activity occurs in this MR, Alpine developers may close it in the future.\n\nThanks for your contribution."
}

By maxice8 on 2021-05-25T09:19:46

Hej,

thanks for the issue. Let me comment on a few of the suggestions.

comment / close stale MRs

Commenting should just work as @maxice8 mentioned. I'm not sure if I would recommend auto-closing MRs since that could be annoying (some MRs just take longer than X days to finish or sometimes the contributor is busy for some weeks but wants to get back to the MR). I'd recommend doing it like Alpine: Automatically label & put a message on stale MRs but manually close it if the contributor doesn't get back to you.

auto-assign users to MRs for their packages, based on "Maintainer:" in APKBUILD

We might have a slight problem here since you're using gitlab.com: aports-qa-bot needs a bot token with admin permissions to search users by email and I don't think one can get those without a self-hosted instance. If the maintainer field were to use the Gitlab user name (or if there were some other mapping between email -> username) we could make it work.

automatically tagging of MRs: aport:upgrade, which release etc.

That should work, we'd just have to add support for pmOS' branch <-> release name mapping.

complain if MRs are coming from a protected branch (e.g. master after forking)

That's also being worked on for Alpine currently.

automatically check "Allow maintainers to edit" (check_mr_settings.py complains about this; if we can instead of complaining just set the checkmark it would be more userfriendly!)

aports-qa-bot currently automatically sets this for users (as in it doesn't matter whether the checkbox is checked or not)

comment / close stale issues too (all postmarketOS git repositories)

Hm, not sure if closing issues automatically is a good idea. Fedora does this for EOL branches and often times when I google for some error I encounter on Fedora I find an existing bug report that was auto-closed by the bot because no maintainer got around to look at it before the branch EOL'ed. On the other hand, with Alpine we're having so many issues that they're pretty likely to be ignored even if they're still relevant, so maybe auto-closing issues that are tagged for EOL'ed branches makes sense for pmOS.

tag device packages too (pmaports.git)

As long as the label is only the pkgname, that should be trivial to implement

By Rasmus Thomsen on 2021-05-25T12:57:33

assigned to @MartijnBraam

By Oliver Smith on 2021-07-13T19:06:58

@MartijnBraam: can you update the status here? (it's running periodically now and assigning stale labels + posting in stale issues/MRs, right? for which repos?)

By Oliver Smith on 2021-08-08T01:10:21

It's running now using the account of @pmgitbot and it's linked to all the repositories in the postmarketOS gitlab organisation. At the moment it's only running the AutoStale service that adds the labels to merge requests after 30 days of inactivity.

The other features require development work so I'm in the process of trying to understand go modules.

By Martijn Braam on 2021-08-15T21:39:42

This is already the case. Closing

closed

Use alpine-qa-bot in postmarketOS

Child items ...

Activity