Learn more about these different git repos.
Other Git URLs
When a user (contributor or maintainer) rebases an open pull request, correctly identify who triggers a rebase instead of defaulting to contributor
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).
I made a screenshot mock-up:
<img alt="Screenshot of a rebase triggered by a maintainer: attribute incorrectly given to contributor" src="/pagure/issue/raw/files/93b3e996285e22db0c04072aa448339d16f3379e45e5b9cb42dd29cab703b51f-Screenshot_2019-03-22_PR15_Split_supporting_mentors_from_the_ideas_page_-_mentored-projects_-_Pagure_io.png" />
<img alt="Screenshot of a rebase triggered by a maintainer: attribute given to maintainer" src="/pagure/issue/raw/files/30f0d4935d83f92c9e62cf36b7d2ea87c2abd63108ae71bece49438070220de8-Screenshot_2019-03-22_PR15_Split_supporting_mentors_from_the_ideas_page_-_mentored-projects_-_Pagure_io1.png" />
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)
Login to comment on this ticket.