Learn more about these different git repos.
Other Git URLs
currently, we should whether it is open/merged closed but, i guess this feature will be good to have
@vivekanand1101 I would like to work on this. Could you please explain more about this ?
@akasurde "My pull request page" is like: https://pagure.io/user/vivekanand1101/requests (that's of mine). There we are displaying "status" in one of the columns. What we can do is show "merge status" so that once you view that page, you will know which PRs you can merge as it is and which PR would need - rebase (if you prefer) or which PR have merge conflicts. We currently show the merge status in PR page only. So, from there you can know which end point is called to get merge status.
Do we refresh the status then or just show the cached one?
@vivekanand1101 As I understand it correctly, we need to have a new column called "Merge Status" which takes values from request.merge_status
request.merge_status
Metadata Update from @pingou: - Issue assigned to akasurde
I would say refresh. But, will it be too costly or time taking?
@vivekanand1101 I think I'd rather we use the cache status for now, if we wanted to refresh it I would see us use another small service for this :)
sure, np.
Fixed by @akasurde in #2039
Metadata Update from @pingou: - Issue close_status updated to: Fixed - Issue status updated to: Closed (was: Open)
Login to comment on this ticket.