Skip to content

update issue triage process to improve Dosu bot quality #43511

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
potiuk merged 1 commit into from
Oct 30, 2024
Merged

update issue triage process to improve Dosu bot quality #43511

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
7 changes: 3 additions & 4 deletions ISSUE_TRIAGE_PROCESS.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -170,18 +170,17 @@ and ``area:providers``. This is especially important since these are now
being released and versioned independently.

There are more detailed areas of the Core Airflow project such as Scheduler, Webserver,
API, UI, Logging, and Kubernetes, which are all conceptually under the
API, UI, Logging, and Metrics, which are all conceptually under the
"Airflow Core" area of the project.

Similarly within Airflow Providers, the larger providers such as Apache, AWS, Azure,
and Google who have many hooks and operators within them, have labels directly
associated with them such as ``provider:Apache``, ``provider:AWS``,
``provider:Azure``, and ``provider:Google``.
associated with them such as ``provider:amazon-aws``, ``provider:microsoft-azure``, and ``provider:google``.

These make it easier for developers working on a single provider to
track issues for that provider.

Some provider labels may couple several providers for example: ``provider:Protocols``
Note: each provider has it's own unique label. It is possible for issue to be tagged with more than 1 provider label.

Most issues need a combination of "kind" and "area" labels to be actionable.
For example:
Expand Down