#850 Implement scripts to perform Forge post-migration tasks
Closed: Fixed by kparal. Opened by kparal.

The idea is that we create scripts that would perform post-migration tasks as listed in #836. Or at least some of them.

I'll combine this with my AI goal and will try to create the scripts using AI generation through Cursor IDE.


At this moment, I have a (seemingly) mostly functional script to comment on Pagure repo tickets "This ticket has been moved to $forge_url".

I'll need to figure out where to store the scripts. New Pagure repo creation is disabled, so I'll either put it into https://pagure.io/fedora-qa/qa-misc or create a separate project in production Forge under our team.

Metadata Update from @kparal:
- Custom field story_points adjusted to 8

Requested project creation re-enablement for Pagure staging:
https://pagure.io/fedora-infrastructure/issue/12943

I placed the generated scripts here:
https://forge.fedoraproject.org/quality/forge-helpers

Currently it can:
a) add a comment to Pagure that a ticket was migrated to Forge URL
b) migrate story points from Pagure to Forge (as labels)

It can also:
c) create fake issues on Pagure (for testing)

In the next days, I need to verify that b) works fine with both repo-level labels (tested) and org-level labels (not tested).

Metadata Update from @kparal:
- Issue assigned to kparal

I'm closing this as done. The existing scripts seem to work well enough and cover our needs.

In the future, we might also need a script that will update labels on our tickets (e.g. going from repo-level labelA to org-level labelB), but that's not an immediate need, I'll open a new ticket for that.

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

This issue has been migrated to Fedora Forge:
https://forge.fedoraproject.org/quality/tickets/issues/850

Please continue any further discussion there.

Metadata