Move the Fedora Badges static assets from Pagure to Forgejo #3347

Merged

ryanlerch merged 1 commit from t0xic0der/ansible:move into main 2026-05-28 02:22:22 +00:00

Conversation 1 Commits 1 Files changed 1 +1 -1

t0xic0der commented 2026-05-13 06:02:15 +00:00

Member

Copy link

Signed-off-by: Akashdeep Dhar akashdeep.dhar@gmail.com

Signed-off-by: Akashdeep Dhar <akashdeep.dhar@gmail.com>

t0xic0der added 1 commit 2026-05-13 06:02:15 +00:00

Move the Fedora Badges static assets from Pagure to Forgejo ... 30f65c9c2e

Signed-off-by: Akashdeep Dhar <akashdeep.dhar@gmail.com>

t0xic0der self-assigned this 2026-05-13 06:02:22 +00:00

t0xic0der added a new dependency 2026-05-13 06:04:45 +00:00

forge/forge#485 - Move Fedora Badges static assets from Pagure to Forgejo

t0xic0der force-pushed move from 30f65c9c2e to 148bce1720 2026-05-14 08:46:27 +00:00 Compare

t0xic0der referenced this pull request from forge/forge 2026-05-18 00:05:24 +00:00

Move Fedora Badges static assets from Pagure to Forgejo #485

t0xic0der force-pushed move from 148bce1720 to c76f95ab40 2026-05-19 03:16:45 +00:00 Compare

t0xic0der changed title from WIP: Move the Fedora Badges static assets from Pagure to Forgejo to Move the Fedora Badges static assets from Pagure to Forgejo 2026-05-25 03:04:14 +00:00

t0xic0der force-pushed move from c76f95ab40 to 0d7a41c5fb 2026-05-25 03:05:56 +00:00 Compare

t0xic0der requested reviews from kevin, zlopez 2026-05-25 03:06:08 +00:00

t0xic0der commented 2026-05-25 03:31:00 +00:00

Author

Member

Copy link

As of 0850am IST, the repository has been moved over from Pagure to Forgejo, and hence, this pull request can now be actioned.

As of 0850am IST, the repository has been moved over from [Pagure](https://pagure.io/fedora-badges) to [Forgejo](https://forge.fedoraproject.org/apps/badges-assets), and hence, this pull request can now be actioned.

t0xic0der referenced this pull request from forge/forge 2026-05-25 03:53:55 +00:00

Move Fedora Badges static assets from Pagure to Forgejo #485

ryanlerch merged commit b8773db5ba into main 2026-05-28 02:22:22 +00:00

t0xic0der referenced this pull request from forge/forge 2026-05-28 03:43:44 +00:00

Move Fedora Badges static assets from Pagure to Forgejo #485

Sign in to join this conversation.

Reviewers

No reviewers

kevin

zlopez

Labels

Clear labels   

ai-review-please

label for requesting AI code review

  

freeze-break-request

  

post-freeze

  

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

ai-review-please

freeze-break-request

post-freeze

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

t0xic0der

1 participant

Notifications

Subscribe

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Blocks

#485 Move Fedora Badges static assets from Pagure to Forgejo

forge/forge

Reference

infra/ansible!3347

No description provided.