Laura Barcziová

> We could react only to the merging of packit rawhide PR but still we will load the gotmax PR (already merged) because it is the first merged and has...

> As far as I understand the documentation [1](https://github.com/packit/packit-service/issues/2359#user-content-fn-1-be60ab1e82627b909e2a1e9e678b596f), if the PR is closed or merged, they are both treated as closed. The property properties.merged seems to be used to...

Yes, as I [wrote previously](https://github.com/packit/packit-service/issues/2359#issuecomment-1978259591), we get all the PRs because previously we were hitting this race condition mentioned in the comment when we were getting only merged PRs. It...

That's true, but it would lead to duplicating of build triggering, as we would receive both messages about closed PR and pushed commit :/

Notes from arch: - we cannot rely on getting the correct PR via API - @nforro had a look into the Pagure code and it should not be that complicated...

> pagure.git.receive listener: checks koji_build for commit triggers, filtering out any commit that belongs to a PR but without changes to the pagure source code, this is still not reliably...

hi @martinpitt @lsm5 ! Thanks for the provided suggestions! Regarding the "draft" point, both options make sense to me and could be added under `failure_comment` : 1. `disable_for_drafts` or similar...

Notes from standup: - this may already be resolved, let's check what is the current situation during next Copr's upgrade

Output from Packit 2023/Q1 planning meeting: - What's the benefit? easier, clearer installation for the users; better UX in general - Who will benefit? all (new) users

This may be a little bit related: https://github.com/packit/packit-service/issues/1754