pagure

#4374 Correctly identify user that triggers a rebase commit in an open pull request
Closed: Duplicate by pingou. Opened by jflory7.

Closed: Duplicate
Reopen Issue

Summary

When a user (contributor or maintainer) rebases an open pull request, correctly identify who triggers a rebase instead of defaulting to contributor

Background

In an open pull request, a maintainer can also choose to rebase the pull request if it falls behind from the upstream target branch. If a maintainer does this, the contributor appears to rebased a pull request.

This can be confusing when a pull request sits for a while and one maintainer chooses to rebase a pull request. If a different maintainer picked up the pull request later, it would help to know if the contributor has been engaged with the pull request recently (instead of rebasing by repo maintainers).

Details

I made a screenshot mock-up:

Current behavior

Screenshot of a rebase triggered by a maintainer: attribute incorrectly given to contributor

Desired behavior

Screenshot of a rebase triggered by a maintainer: attribute given to maintainer

Outcome

Better clarity about contributor and maintainer engagement in pull requests
<!!image>

Thank you for your report, this is however a duplicate of https://pagure.io/pagure/issue/4316

It has been fixed in the development of the 5.5 release and will be released as part of it.

Thanks for your ticket though, it is always appreciated :)

Metadata Update from @pingou:
- Issue close_status updated to: Duplicate
- Issue status updated to: Closed (was: Open)
Metadata
None
None
None
None
None
Static archive. pagure.io was sunset in 2026; this is a read-only snapshot.
Red Hat Logo

Fedora is sponsored by Red Hat. Learn more about the relationship between Red Hat and Fedora »

© Red Hat, Inc. and others.