Gabriel Wicki <[email protected]> writes: > pinoaffe <[email protected]> writes: > >> This is very cool work! > Thank you! > >> I have a few questions: >> - how can the bot-PRs be recognized as such? >> - what account(s) will the bots use to open PRs? > It tells you so, both with the PR author's name as well as the content > (and the for-its-purpose adjusted PR message). > > See the Pull Requests if you need more insight > (and understandably don't care to skim the source), here: > https://codeberg.org/guix/guix/pulls?q=&type=all&sort=relevance&state=open&labels=&milestone=0&project=0&assignee=0&poster=1339987 > >> - what rate-limiting is built in, to prevent guix from being flooded >> with PRs? > None. Why would guix be flooded with PRs? The way the bot is > implemented is to run our internal tools as intended, sequentially, > and—when successful—also build the `-P 1` dependents and only then push > the PR. *Iff* all steps go well there is 1 single PR for each package > it's been started for. > > It does not cycle or keep going after attempting to upgrade once. So, > worst (or best?) case would be 1 PR for every package (e.g. in a module, > like I let it run before my holidays).
Should the updates be carried out in batches that are relevant to each other? It's only been a few hours, now there are over 20+ messages in my inbox, every pr are only one commit.
signature.asc
Description: PGP signature
