[BUG] Bot does not re-evaluate PR if it is not by the user who added it

[hasezoey]

Describe the bug

From what i can tell, the cocogitto bot does not re-evaluate a PR if a user has pushed (or even force pushed) to a PR, but seemingly does if it is done by either the repository owner or the user who added it (i am not sure).

To Reproduce

I am no entirely sure, aside from having a personal repository in user A and user B.

• with User B open a new PR with changes which conflict
• observe bot commenting with a issue and having the O status check
• with User B force-push changes which fix the mentioned issues
• observe bot not updating the message or the status check

Expected behavior
To re-evaluate once new changes are available

Additional context
Originally observed in:
User B showcase:

• Remove feature clipboard from textarea veeso/tui-realm#188
• Slight cleanup veeso/tui-realm#187 (observe the bot still being O status check)
• Apply changes for ratatui 0.30 veeso/tui-realm-stdlib#53
• Remove usage of core Dataset veeso/tui-realm-stdlib#52

User A showcase:

• refactor: cleanup exports, module-level only (#168) veeso/tui-realm#182 (never had conflicts, but Green status check)
• fix(treeview): backport upstream fixes veeso/tui-realm#181 (same here)
• fix: Textarea::perform returns CmdResult::Changed on state change veeso/tui-realm#186
  (in the first 2 of the above PRs i observed cocogitto removing the old comments and adding new ones on push, even force-push)

Note that i dont have access to modify the bot configuration more than the cog.toml, which we dont currently set.

PS: is this bot development still active, considering the last update is about 2 years ago?

[hasezoey]

Slight update, for some reason there is now a PR with User B scenario where the status check is actually green:

• Add missing PropValue functions veeso/tui-realm#192

[oknozor]

Hey @hasezoey, thanks for the report.

Yes bot development is still active, but I am currently focusing on splitting cocogitto itself into multiple smaller crates so its easier to reuse in the bot.

When I am done with that I will focus on improving the bot.
Meanwhile PR are more than welcome.