#1603 Regenrating tickets repo when 0 tickets in db should recreate tickets repo/go back to 0 commits
Closed: Fixed 7 years ago Opened 7 years ago by vivekanand1101.

It will be helpful, if in case someone, even after giving twice the instructions forgets/ignores to install the "Pagure Tickets" plugin.

The change should go somewhere around here: https://pagure.io/pagure/blob/master/f/pagure/ui/repo.py#_1714 (if, in case this ticket is accepted)


hm, I am not sure to follow the idea, could you expand a little the problem and the solution you're proposing?

Problem: Once someone pushes to remote (the pagure ticket repo of the project) without the Pagure Tickets plugin on, there is currently no way that one can create the tickets without having to delete the project.

Solution: There is an option for regenerating the tickets repo. I have not been able to use that option till now :/ . I know that it updates the repo with the tickets in database. It probably makes commits on top of the existing commits. What i think is: during regeneration, if we recreate the repo and then start updating it with the tickets/requests in database, then this regenerating option can be used by people who forgot to turn on the plugin before pushing. They can regenerate and push again. It will help in both the cases: if there were no tickets or if there were few tickets before pushing.

Metadata Update from @vivekanand1101:
- Issue close_status updated to: Fixed
- Issue status updated to: Closed (was: Open)

7 years ago

Login to comment on this ticket.

Metadata