scm_request - migrate ticket handling to Fedora Forge #429

Merged

zlopez merged 5 commits from jnsamyak/toddlers:migrate_scm_requests into main 2026-08-05 12:48:55 +00:00

Conversation 10 Commits 5 Files changed 14 +2084 -608

jnsamyak commented 2026-07-14 11:46:51 +00:00

Owner

Copy link

Please check issue for more details: releng/tickets#13370 (comment)

Please check issue for more details: https://forge.fedoraproject.org/releng/tickets/issues/13370#issuecomment-1062204

jnsamyak added 3 commits 2026-07-14 11:46:52 +00:00

[migration2forgejo]feat: add thin Forgejo issue API client ... 76e1738ce0

Signed-off-by: Samyak Jain <samyak.jn11@gmail.com>

[migration2forgejo]feat: add W2FM issue topic helpers and normalizer ... 98ac6402ac

Signed-off-by: Samyak Jain <samyak.jn11@gmail.com>

[migration2forgejo]feat: process Forgejo tickets via forgejo util ... 6bbae261e7

Signed-off-by: Samyak Jain <samyak.jn11@gmail.com>

jnsamyak changed title from WIP: scm_request - migrate ticket handling to Fedora Forge to scm_request - migrate ticket handling to Fedora Forge 2026-07-14 14:29:38 +00:00

jnsamyak force-pushed migrate_scm_requests from 6bbae261e7 to e9478125cc 2026-07-14 14:42:33 +00:00 Compare

jnsamyak added 1 commit 2026-07-14 16:34:45 +00:00

[migration2forgejo]fix: make Forgejo SCM CI green (black, mypy, coverage) ... c6d6a8624c

Signed-off-by: Samyak Jain <samyak.jn11@gmail.com>

jnsamyak commented 2026-07-14 16:35:12 +00:00

Author

Owner

Copy link

Added a set of more tests to make CI happy, and had some formatting issues.

Added a set of more tests to make CI happy, and had some formatting issues.

jnsamyak commented 2026-07-14 16:36:54 +00:00

Author

Owner

Copy link

I think for reviews, the tests/ can be ignored for now, and we can jump back on the actual code to see if I'm missing any race conditions.

I think for reviews, the tests/ can be ignored for now, and we can jump back on the actual code to see if I'm missing any race conditions.

image.png

31 KiB

jnsamyak requested reviews from lenkaseg, kevin, james, zlopez 2026-07-14 16:39:46 +00:00

jnsamyak commented 2026-07-14 16:41:29 +00:00

Author

Owner

Copy link

But this change is to wait for fedpkg changes happening at releng/tickets#13369, I want to make sure to have things ready so we can test it out once we have fedpkg changes in.

But this change is to wait for fedpkg changes happening at https://forge.fedoraproject.org/releng/tickets/issues/13369, I want to make sure to have things ready so we can test it out once we have fedpkg changes in.

jnsamyak referenced this pull request from releng/tickets 2026-07-14 16:54:26 +00:00

Migration of fedora-scm-requests to Forgejo #13108

jnsamyak commented 2026-07-14 17:25:52 +00:00

Author

Owner

Copy link

Merging #430 for Anton, I think this PR will grow because I haven't accounted for unretirement toddler changes also, but I'll let it sit for one set of review.

Merging #430 for Anton, I think this PR will grow because I haven't accounted for unretirement toddler changes also, but I'll let it sit for one set of review.

kevin referenced this pull request from releng/tickets 2026-07-14 21:13:11 +00:00

Migration of fedora-scm-requests to Forgejo #13108

jnsamyak added 1 commit 2026-07-20 06:06:38 +00:00

[migration2forgejo] handle unretirement tickets via Forgejo ... 304bd230ec

Move unretire_packages ticket lifecycle off pagure.io onto Forge
(forgejo.issues), keeping dist-git/koji/bodhi unchanged.

Signed-off-by: Samyak Jain <samyak.jn11@gmail.com>

jnsamyak commented 2026-07-20 06:08:16 +00:00

Author

Owner

Copy link

I pushed changes for unretirement toddler as well, so unretirement tickets on releng/fedora-scm-requests are handled via Forgejo (forgejo.issues) instead of pagure.io. Dist-git, koji, and bodhi are unchanged. @amedvede would be nice if you could take a look at it.

I pushed changes for unretirement toddler as well, so unretirement tickets on releng/fedora-scm-requests are handled via Forgejo (forgejo.issues) instead of pagure.io. Dist-git, koji, and bodhi are unchanged. @amedvede would be nice if you could take a look at it.

jnsamyak force-pushed migrate_scm_requests from 304bd230ec to b76f19fb00 2026-07-20 13:44:07 +00:00 Compare

jnsamyak commented 2026-07-20 13:44:43 +00:00

Author

Owner

Copy link

Added a test, and cosmetic changes to make CI green, let's see

Added a test, and cosmetic changes to make CI green, let's see

amedvede referenced this pull request from releng/tickets 2026-07-21 08:23:56 +00:00

[fedora-scm-requests] - Migrate scm-request related stuff in toddlers to support the new forge #13370

patrikp referenced this pull request from packaging/fedpkg 2026-07-29 07:57:14 +00:00

Migrate SCM requests from Pagure to Forgejo #636

zlopez approved these changes 2026-08-04 12:13:14 +00:00

zlopez left a comment

Copy link

I went through the changes and they look good to me.

I went through the changes and they look good to me.

jnsamyak referenced this pull request from releng/tickets 2026-08-04 18:20:08 +00:00

Migration of fedora-scm-requests to Forgejo #13108

jnsamyak commented 2026-08-05 12:22:25 +00:00

Author

Owner

Copy link

Thanks, I'll merge this up. @zlopez should I just cherry-pick these to staging and production directly or open PRs?

Thanks, I'll merge this up. @zlopez should I just cherry-pick these to staging and production directly or open PRs?

jnsamyak commented 2026-08-05 12:22:48 +00:00

Author

Owner

Copy link

Also just merge this, or squash out the commits?

Also just merge this, or squash out the commits?

zlopez commented 2026-08-05 12:48:49 +00:00

Owner

Copy link

@jnsamyak wrote in #429 (comment):

Thanks, I'll merge this up. @zlopez should I just cherry-pick these to staging and production directly or open PRs?

I think that the staging and production branch should now be at the same head as master, so there should be no need for cherry pick.

@jnsamyak wrote in #429 (comment):

Also just merge this, or squash out the commits?

Let me just merge this.

@jnsamyak wrote in https://forge.fedoraproject.org/apps/toddlers/pulls/429#issuecomment-1081017: > Thanks, I'll merge this up. @zlopez should I just cherry-pick these to staging and production directly or open PRs? I think that the staging and production branch should now be at the same head as master, so there should be no need for cherry pick. @jnsamyak wrote in https://forge.fedoraproject.org/apps/toddlers/pulls/429#issuecomment-1081018: > Also just merge this, or squash out the commits? Let me just merge this.

zlopez merged commit b76f19fb00 into main 2026-08-05 12:48:55 +00:00

Sign in to join this conversation.

Reviewers

No reviewers

lenkaseg

kevin

james

zlopez

Labels

Clear labels   

cle

Tickets that should be addressed by CLE Team

  

EasyFix

Good first issue to start on

  

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.

  

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

cle

EasyFix

Backlog Status

Needs Review

Backlog Status

Ready

chore

documentation

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

Assignees

Clear assignees

No assignees

2 participants

Notifications

Subscribe

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

apps/toddlers!429

No description provided.