forge/forge
11
8
Fork 6
Code Issues 93 Pull requests Projects 2 Wiki Activity Actions

Retroactively resolve the pull request commit histories across migrated repositories #570

New issue
Closed
opened 2026-05-14 08:53:58 +00:00 by t0xic0der · 1 comment
t0xic0der commented 2026-05-14 08:53:58 +00:00
Member
Copy link

Summary

Retroactively resolve the pull request commit histories across migrated repositories

Details

Retroactively resolve the pull request commit histories across migrated repositories

After the https://codeberg.org/forgejo/forgejo/pulls/12433 lands on the production environment, any newly migrated pull requests would have their complete commit histories but the ones that have already migrated will not.

We need to be able to retroactively be able to resolve the commit histories of the pull requests that have already made it across to the other side. While it could first help the Koji migration but then it could help other repos too.

### Summary Retroactively resolve the pull request commit histories across migrated repositories ### Details Retroactively resolve the pull request commit histories across migrated repositories After the https://codeberg.org/forgejo/forgejo/pulls/12433 lands on the production environment, any newly migrated pull requests would have their complete commit histories but the ones that have already migrated will not. We need to be able to retroactively be able to resolve the commit histories of the pull requests that have already made it across to the other side. While it could first help the Koji migration but then it could help other repos too.
ryanlerch added this to the Backlog project 2026-05-18 10:17:50 +00:00
ryanlerch modified the project from Backlog to Sprint 21 2026-05-18 10:21:04 +00:00
ryanlerch commented 2026-06-01 07:03:08 +00:00
Owner
Copy link

The fix is live, and the script can be run now on the server to repair incorrect PRs.

forgejo doctor pagure-pull-requests --owner koji --repo koji-tools --fix
The fix is live, and the script can be run now on the server to repair incorrect PRs. ``` forgejo doctor pagure-pull-requests --owner koji --repo koji-tools --fix ```
Sign in to join this conversation.
No Branch/Tag specified
Branches Tags
main
test
docs
No results found.
Labels
Clear labels   
Backlog Status
Needs Review
 Work items that have been created or updated but need review, refinement, or approval before they can be considered ready for sprint planning.

  
Backlog Status
Ready
 Work items that have been reviewed, refined, and are ready to be committed to a sprint. These items have clear requirements and could be worked on immediately when capacity is available.

  
Chore
Tasks that are necessary but don't directly deliver new value to the end-user. These are internal tasks like updating a library, managing user accounts, or setting up a new service.

  
points
01
 A task that is simple, small, and has very little uncertainty. It should be easy enough for any team member to pick up and complete quickly, without a lot of discussion or research.

  
points
02
 This is a task that is slightly more complex or larger than a "1." It might involve two or three simple steps, but the outcome is still very clear and there's little uncertainty.

  
points
03
 medium-sized task with some noticeable complexity. It might require a bit more thought or collaboration. The steps are well-defined, but it's not a trivial change.

  
points
05
 a significant piece of work. It has more complexity and a higher degree of uncertainty than smaller tasks. It might require some research, a design discussion, or collaboration across multiple teams.

  
points
08
 complex task with a lot of uncertainty. It's often the largest size that a team will consider for a single sprint. It likely requires a detailed breakdown and multiple team members to complete.

  
points
13
 Any task that feels like it's a "13" or more is considered an Epic. These are too large and uncertain to be worked on in a single sprint.

  
Priority
High
 This is for work that is critical and needs to be addressed in the next sprint. It's often for urgent bugs, important features, or a major piece of technical debt that is blocking other work.

  
Priority
Low
 This is for work that is good to do but not urgent. It's a candidate for being worked on when there's extra time or when it rises in importance. It can stay in the backlog for a longer period.

  
Priority
Medium
 This is for important work that should be done soon, but isn't as urgent as a high-priority item. It will likely be considered for the next 1-2 sprints.

  
Sprint Status
Blocked
 Indicates the work cannot proceed. There is a dependency or an issue that is preventing the team from completing the task. This is a flag for the Scrum Master to help unblock the team.

  
Sprint Status
Done
 Work items that have been completed, reviewed, and integrated. No further work is needed within the current sprint.

  
Sprint Status
In Progress
 This label is for work that a developer is actively working on. This is usually what you'll see on the "In Progress" column of your project board.

  
Sprint Status
Review
 This indicates that the work is complete, but it is now in a review state. This could mean a peer code review, a QA check, or a review by the Product Owner.

  
Sprint Status
To Do
 Work items that are committed to the sprint but haven't been started yet. These items are ready to be picked up by team members.

  
Technical Debt
work that improves the codebase without adding new features. It's work that pays down the "debt" you've accumulated, such as refactoring a messy piece of code, improving test coverage.

  
Work Item
Bug
 Issues where the system is not working as intended or designed. Bugs represent deviations from expected behavior.

  
Work Item
Epic

  
Work Item
Spike

  
Work Item
Task

  
Work Item
User Story

No labels
Backlog Status
Needs Review
Backlog Status
Ready
Chore
points
01
points
02
points
03
points
05
points
08
points
13
Priority
High
Priority
Low
Priority
Medium
Sprint Status
Blocked
Sprint Status
Done
Sprint Status
In Progress
Sprint Status
Review
Sprint Status
To Do
Technical Debt
Work Item
Bug
Work Item
Epic
Work Item
Spike
Work Item
Task
Work Item
User Story
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Sprint 21
Assignees
Clear assignees
No assignees
ryanlerch
2 participants
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
forge/forge#570
No description provided.