Replies: 4 comments
-
|
From what I’ve seen, |
Beta Was this translation helpful? Give feedback.
-
|
While working on the CI setup, we also discussed strategies for automating Issue & PR labeling. Related context: #11 (comment) We initially considered a rule-based approach, but Dosu was integrated quickly (thanks to @eazyhozy), allowing us to experiment directly with an AI-powered workflow. (This is still an early-stage choice and not a fixed decision.) |
Beta Was this translation helpful? Give feedback.
-
|
FYI: How dosu is connected to GitHub At the moment, the dosu instance connected to this repository is authorized via the personal GitHub account @eazyhozy.
|
Beta Was this translation helpful? Give feedback.
-
|
Closing—currently using Dosu-based labeling, which is working well. Further improvements can be discussed separately. |
Beta Was this translation helpful? Give feedback.


Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
Purpose
This discussion explores options for automating issue and pull request management for this project (related to #11).
As the project becomes open-source, we want a simple and scalable way to handle contributions, starting with issue and PR labeling.
Approaches Seen in Other Projects
Rule-based automation (e.g.
actions/labeler)AI-powered automation (e.g.
dosubot)Proposed Direction (Open for Discussion)
A possible phased approach:
actions/labeler) for basic structure.This is a proposal, not a decision.
Feedback Requested
Please share any experiences or suggestions.
Beta Was this translation helpful? Give feedback.
All reactions