quality/forge-helpers
6
0
Fork 1
Code Issues Pull requests Releases Activity Actions

Add forge_convert_labels.py to convert to templated labels (#1) #3

Manually merged
kparal merged 0 commits from label-convert into main 2026-04-29 10:56:53 +00:00
Conversation 7 Commits - Files changed -
adamwill commented 2026-02-10 02:39:13 +00:00
Owner
Copy link

As part of the Pagure migration process, per-repo labels were
created to match Pagure's labels, priorities and statuses. But
in Forgejo we also have similar quality org-wide labels templated
from instance-wide labels, which is confusing and redundant.

This script runs on a Forgejo repo and removes the per-repo
priority labels, replacing them with the templated priority
labels. It also replaces 'bug' with 'Work Item/Bug' and
'task' with 'Work Item/Task', since they seem pretty good
equivalents.

We use color to distinguish between the per-repo and templated
priority labels as they actually have the exact same names. The
colors for the 'bug' and 'task' labels seem pretty consistent
from repo to repo, except one outlier where the 'task' color
was different; it's easy to edit on the fly if necessary.

Signed-off-by: Adam Williamson awilliam@redhat.com

As part of the Pagure migration process, per-repo labels were created to match Pagure's labels, priorities and statuses. But in Forgejo we also have similar quality org-wide labels templated from instance-wide labels, which is confusing and redundant. This script runs on a Forgejo repo and removes the per-repo priority labels, replacing them with the templated priority labels. It also replaces 'bug' with 'Work Item/Bug' and 'task' with 'Work Item/Task', since they seem pretty good equivalents. We use color to distinguish between the per-repo and templated priority labels as they actually have the exact same names. The colors for the 'bug' and 'task' labels seem pretty consistent from repo to repo, except one outlier where the 'task' color was different; it's easy to edit on the fly if necessary. Signed-off-by: Adam Williamson <awilliam@redhat.com>
As part of the Pagure migration process, per-repo labels were
created to match Pagure's labels, priorities and statuses. But
in Forgejo we also have similar quality org-wide labels templated
from instance-wide labels, which is confusing and redundant.

This script runs on a Forgejo repo and removes the per-repo
priority labels, replacing them with the templated priority
labels. It also replaces 'bug' with 'Work Item/Bug' and
'task' with 'Work Item/Task', since they seem pretty good
equivalents.

We use color to distinguish between the per-repo and templated
priority labels as they actually have the exact same names. The
colors for the 'bug' and 'task' labels seem pretty consistent
from repo to repo, except one outlier where the 'task' color
was different; it's easy to edit on the fly if necessary.

Signed-off-by: Adam Williamson <awilliam@redhat.com>
kparal self-assigned this 2026-02-10 15:08:07 +00:00
kparal requested review from kparal 2026-02-10 15:08:23 +00:00
kparal added this to the Sprint 3 project 2026-02-10 16:12:35 +00:00
kparal removed this from the Sprint 3 project 2026-02-24 16:32:13 +00:00
mikem commented 2026-04-22 00:01:33 +00:00
First-time contributor
Copy link

This script is referenced in the forge migration docs, but this PR is still unmerged. Is it ready for use?

This script is referenced in the [forge migration docs](https://docs.fedoraproject.org/en-US/forge-documentation/migration/pagure_repository/#_next_steps), but this PR is still unmerged. Is it ready for use?
adamwill commented 2026-04-22 04:41:27 +00:00
Author
Owner
Copy link

@kparal ? Was still waiting on your review, I guess.

As far as I'm concerned it's fine to use, but you might have to tweak it a bit to match the labels you actually want/need to migrate for your org/projects.

@kparal ? Was still waiting on your review, I guess. As far as I'm concerned it's fine to use, but you might have to tweak it a bit to match the labels you actually want/need to migrate for your org/projects.
kparal commented 2026-04-22 08:10:54 +00:00
Owner
Copy link

Sigh, sorry, wanted to do it after the F44 cycle. But since Adam tested it in a real-world usage already, I'll just merge this ASAP. I can do a more detailed review later, if there's time. (I originally wanted to make it a bit more flexible, but that can happen some other time).

@adamwill Would you be so kind and add a short usage example into README as part of this PR, before I merge this?

Sigh, sorry, wanted to do it after the F44 cycle. But since Adam tested it in a real-world usage already, I'll just merge this ASAP. I can do a more detailed review later, if there's time. (I originally wanted to make it a bit more flexible, but that can happen some other time). @adamwill Would you be so kind and add a short usage example into README as part of this PR, before I merge this?
kparal added this to the Sprint 8 project 2026-04-22 08:11:15 +00:00
kparal requested changes 2026-04-27 08:56:12 +00:00
kparal left a comment
Copy link

Please add a README example with a couple of useful hints on how a general audience can use this, thanks.

Please add a README example with a couple of useful hints on how a general audience can use this, thanks.
adamwill force-pushed label-convert from f0354e1d80 to 9cd4def047 2026-04-29 02:14:42 +00:00 Compare
adamwill commented 2026-04-29 02:15:12 +00:00
Author
Owner
Copy link

I went a bit further and split the replacements mapping out into a JSON file that can be replaced, so it's easier to use this for other orgs/repos. And added the doc section.

I went a bit further and split the replacements mapping out into a JSON file that can be replaced, so it's easier to use this for other orgs/repos. And added the doc section.
adamwill commented 2026-04-29 02:15:56 +00:00
Author
Owner
Copy link

maybe I should use Path instead of str for this...meh.

maybe I should use Path instead of str for this...meh.
kparal force-pushed label-convert from 9cd4def047 to 79855da7be 2026-04-29 10:53:07 +00:00 Compare
kparal manually merged commit 79855da7be into main 2026-04-29 10:56:53 +00:00
kparal deleted branch label-convert 2026-04-29 10:57:16 +00:00
kparal commented 2026-04-29 10:58:36 +00:00
Owner
Copy link

Thanks, merged.

Btw, adding new commits during review is better for comparing changes, rather than rewriting commits and force-pushing. The PR can be squashed before merging.

Thanks, merged. Btw, adding new commits during review is better for comparing changes, rather than rewriting commits and force-pushing. The PR can be squashed before merging.
Sign in to join this conversation.
Reviewers
No reviewers
kparal
Labels
Clear labels
  
ai-review-please
Request AI review for a pull request

  
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 can be worked on immediately when capacity is available.

  
chore
Work that needs to be done but doesn't add new functionality or fix bugs. Maintenance tasks that keep the system running smoothly and the codebase clean.

  
documentation
Work focused on creating, updating, or improving documentation for users, developers, or system administrators.

  
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 and should be broken down.

  
pr2jira
Sync this pull request to Jira for Agility tracking. Only use for PRs without a corresponding ticket.

  
Priority
Critical
 This is for work that is urgent and of critical importance and so and must be addressed immediately with a higher priority than all other work, even if not originally planned for the current 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
 Work items that cannot progress due to external dependencies, blockers, or issues that need resolution.

  
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
 Work items currently being worked on by a team member. Active development, research, or implementation is happening.

  
Sprint Status
Review
 Work items that are complete but need review, testing, or approval before being marked as done.

  
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 addresses shortcuts, workarounds, or suboptimal implementations that were done previously to meet deadlines. These items improve code quality, maintainability, or performance without adding new features.

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

  
Work Item
Epic
 Large initiatives that are broken down into multiple smaller work items (user stories, tasks, bugs). Epics represent significant features or projects that span multiple sprints.

  
Work Item
Spike
 Time-boxed research, investigation, or proof-of-concept work to reduce uncertainty or explore solutions. Spikes help inform future development decisions.

  
Work Item
Task
 Used to break down larger user stories into smaller, manageable implementation pieces. They focus on the specific technical steps needed to deliver the user story's value.

  
Work Item
User Story
 User-facing features or functionality that can be framed from a user perspective, describing what someone wants to accomplish and why.

No labels
ai-review-please
Backlog Status
Needs Review
Backlog Status
Ready
chore
documentation
points
01
points
02
points
03
points
05
points
08
points
13
pr2jira
Priority
Critical
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 8
Assignees
Clear assignees
No assignees
kparal
adamwill
3 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
quality/forge-helpers!3
No description provided.