META GitHub Bot

[moul]

Do not hesitate to let me know if individual issues could be clearer, but I believe it's better to avoid the noise.

[moul]

So, here, I clicked on "the pull request description", then the bot switched back to unchecked. Should be persisted.

[moul]

Please change the logo; it is generally poor and not suitable for small sizes.

[moul]

The introduction should be aimed at those who are not familiar with the bot. It could say something like, "I'm a bot that assists the core team in maintaining this repository.

followed by the details."

Remove the h1.

[moul]

Group the two "details" into a single "debug" at the end.

[aeddi]

So, here, I clicked on "the pull request description", then the bot switched back to unchecked. Should be persisted.

Morgan already pinged me about this. The bot unchecks because it can't fetch the list of members from the core-contributors team, so it can't verify if you're allowed to check. It might be a token issue, I'll look into it today.

Also this one is weird: https://github.com/gnolang/gno/actions/runs/12072757244

Please change the logo; it is generally poor and not suitable for small sizes.

The introduction should be aimed at those who are not familiar with the bot. It could say something like, "I'm a bot that assists the core team in maintaining this repository."

Group the two "details" into a single "debug" at the end.

Ok 👍

[aeddi]

Another issue: https://github.com/gnolang/gno/actions/runs/12082335167/job/33693214789?pr=3096

Error: unable to update pull request: unable to create status on PR 3096: POST https://api.github.com/repos/gnolang/gno/statuses/2516635949b9e0b19e9b6a4c04115cf6fbf877c4: 403 Resource not accessible by personal access token []

[moul]

🔴 The pull request head branch must be up-to-date with its base

This is already blocked by GitHub settings.

You can keep the check if you believe the bot explains it better, but it shouldn't block the merge. It should be marked "orange" to indicate a warning.

[aeddi]

🔴 The pull request head branch must be up-to-date with its base

This is already blocked by GitHub settings.

You can keep the check if you believe the bot explains it better, but it shouldn't block the merge.

@moul I can disable it, just added it because it was one of the rule requested initially here, I think we should probably merge the fixes here first and then fine-tune the configuration.

It should be marked "orange" to indicate a warning.

I replaced all orange / pending / warning statuses by red / failed after answering this comment (see the response), basically for Github orange means "processing" and red means "failure" or "requirements not met". The CI is red when you don't have enough review yet for example (which is not an error but just an unmet requirement).

[aeddi]

Please change the logo; it is generally poor and not suitable for small sizes.

What about this one?

New avatar

[thehowl]

This is already blocked by GitHub settings.

Actually, not anymore; I don't recall exactly why, but this was disabled some short while ago.

[aeddi]

I always have this message in the checks of my PR:

Do you think it’s not blocking / that it doesn’t put the CI in "failure" state if everything else is green?