Learn more about these different git repos.
Other Git URLs
Allow the UI to display edit history of issue descriptions and comments. This allows the description to remain a clean representation of the current state while still enabling those who are interested to see the past states. This is important for using Pagure to track Fedora Changes.
Metadata Update from @ryanlerch: - Issue tagged with: RFE
This is also important as we conduct more and more of our project conversation in pagure tickets. I'd love to see a UI which shows the whole edit history clearly, a la that used by Stack Exchange.
I have a vague idea about how Pagure works, but I assumed issues are stored in git repo (a "hidden" one) for anti-vendor-lockin. Is that true?
It is. In the new Pagure UI that's forthcoming, those Git URLs will be listed for people to be able to clone, too.
They already are listed, but only people with commit access can clone the ticket git repo (since it can contain private ticket that only people with commit access can see).
Now that we have the file history view (as of Pagure 5.9), I wonder what would it take to implement history for tickets now? As they are stored as files in a Git repo, could we take advantage of that?
Metadata Update from @wombelix: - Issue set to the milestone: 6.0
Login to comment on this ticket.