quality/blockerbugs

Fork

You've already forked blockerbugs

Code Issues 32 Pull requests 2 Projects 1 Releases Activity Actions

Can Forge Actions replace our discussion processing bot? #298

New issue

Open

opened 2026-03-10 14:25:21 +00:00 by kparal · 0 comments

kparal commented

2026-03-10 14:25:21 +00:00

Owner

Copy link

Let's explore whether Forgejo Actions can replace or simplify our discussion processing bot. They're said to be very powerful.

Let's explore whether [Forgejo Actions](https://forgejo.org/docs/next/user/actions/reference/) can replace or simplify our discussion processing bot. They're said to be very powerful.

kparal added the

labels

2026-03-10 14:25:21 +00:00

jgroman referenced this issue

2026-03-10 14:36:26 +00:00

Switch from Pagure to Forge for blocker review discussions #296

kparal referenced this issue

2026-03-10 14:57:17 +00:00

Switch from Pagure to Forge for blocker review discussions #296

No Branch/Tag specified

develop

staging

master

discussion_link_bz

feature/sync_in_admin_ui

flask_middleware_oc

feature/bugdeps2

kparal/selfref

1.16

1.15

1.14

1.13

1.12

1.11

1.10

1.9

1.8

1.7

1.6.1

1.6

1.5

1.4.1

1.4.0

1.3.1

1.3.0

1.2.1

1.2.0

1.1.0

1.0.0

0.7.4

0.7.3

0.7.2

0.7.1

0.7.0

0.6.1

0.6.0

0.5.0

0.4.15

0.4.14

0.4.13

0.4.12

0.4.4.11-1

0.4.4.11

0.4.4.10

0.4.4.7

0.4.4.6

0.4.4.5

0.4.4.3

0.4.4.2

0.4.4.1

0.4.4

0.4.3.6

0.4.3.5

0.4.3.4

0.4.3.3

0.4.3.1

0.4.3

0.4.2

0.4.1

0.4.0

0.3.0.3.4

t414-infrareviewfix

t414-proposalfix

0.3.0.3

0.3.0.2

0.3.0.1

0.3.0

0.2.5

Labels

Clear labels

Closed As

Duplicate

Closed with the reason of Duplicate

Closed As

Fixed

Closed with the reason of Fixed

Closed As

Invalid

Closed with the reason of Invalid

discussions

easyfix

enhancement

a request for or implementation of an enhancement (not a bug fix)

task

issue that isn't a bug fix or enhancement but some kind of admin task

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

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

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

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

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

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

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

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

Milestone

Clear milestone

No items

No milestone

Projects

Clear projects

No items

No project

Assignees

Clear assignees

No assignees

1 participant

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/blockerbugs#298

Reference in a new issue

Repository

quality/blockerbugs

Title

Body

No description provided.

Delete branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?

Rows
Columns