Alžběta Kučerová
Alžběta Kučerová
This is probably just a nitpick, but this docstring should probably be edited to mention Forgejo webhooks, not just GitHub and GitLab. I would just add Forgejo inside the brackets...
Yes, this was discovered last week. @mfocko opened a [PR for this](https://github.com/packit/ogr/pull/942), which is currently blocked.
It might be worth mentioning that the second link (to use functionality from) gives a 404 error.
I'll try to look into this.
I looked into it and my current understanding is this: A check run is associated with a specific commit, not the PR that the check was triggered in. When Packit...
Or instead, if this kind of situation was to occur and there would be multiple Packit check runs associated with the same commit across multiple PRs, I would mark each...
> `Packit-as-a-Service` is a name of the app Oh, I didn't realize that. Wouldn't the following be also an option? - Before creating a new check run for a commit,...
Alright, shall I move this back to backlog then, since no good solution to this was found?
> Where do I get the push event? Otherwise, it seems we still need the ogr changes for the pull-request trigger, the webhook does not have equivalent data. Could you...
> Sure, when I was looking at this, I couldn't find the appropriate mixin that can be used with Checker so that we have the Commit class that would now...