chore(github): needs-triage on new issues + area/{keycloak,tenant,kamaji} labels by lexfrei · Pull Request #3165 · cozystack/cozystack

Aleksei Sviridkin (lexfrei) · 2026-07-01T10:35:10Z

What this PR does

Two label-housekeeping changes:

Auto-label new issues triage/needs-triage. Both issue templates append triage/needs-triage to their frontmatter labels, so every issue opened through a template lands with a visible "needs triage" marker. blank_issues_enabled: false routes all new issues through a template, so this covers the entire intake — one label to filter the untriaged backlog and a clear signal to act on before the stale bot's 60-day clock elapses.
New area/* labels for recurring scopes. Three scopes recur across the PR history with no fitting area/* — keycloak, tenant, kamaji — so this adds area/keycloak, area/tenant, area/kamaji to labels.yml and maps their scopes in the auto-labeler. It also fills two gaps in existing mappings: mongodb → area/database, csi → area/storage. Existing PRs in these scopes were re-labeled off area/uncategorized.

Release note

NONE

Summary by CodeRabbit

Issue Management
- Bug reports and feature requests are now automatically marked as needing triage.
- Added area labels for Kamaji, Keycloak, and tenants.
- Expanded pull request auto-labeling for database, storage, Kamaji, Keycloak, and tenant changes.

gemini-code-assist · 2026-07-01T10:35:20Z

Summary of Changes

Hello, I'm Gemini Code Assist¹! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request streamlines the issue management process by ensuring that all new issues created via templates are automatically tagged for triage. This provides maintainers with a consistent way to filter and address incoming reports and requests, improving visibility into the untriaged backlog.

Highlights

Automated Triage Labeling: Updated issue templates to automatically apply the 'triage/needs-triage' label to all new issues upon creation.

New Features

🧠 You can now enable Memory (public preview) to help Gemini Code Assist learn from your team's feedback. This makes future code reviews more consistent and personalized to your project's style. Click here to enable Memory in your admin console.

Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature	Command	Description
Code Review	`/gemini review`	Performs a code review for the current pull request in its current state.
Pull Request Summary	`/gemini summary`	Provides a summary of the current pull request in its current state.
Comment	Gemini (@gemini-code-assist)	Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help	`/gemini help`	Displays a list of available commands.

Customization

To customize the Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counterproductive. You can react with 👍 and 👎 on Gemini (@gemini-code-assist) comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for GitHub and other Google products, sign up here.

Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution. ↩

coderabbitai · 2026-07-01T10:35:29Z

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro

Run ID: 048ad97a-4c29-4e9c-8dde-abdf50855dec

📥 Commits

Reviewing files that changed from the base of the PR and between 3e9fd75 and 9034206.

📒 Files selected for processing (4)

.github/ISSUE_TEMPLATE/bug_report.md
.github/ISSUE_TEMPLATE/feature_request.md
.github/labels.yml
.github/workflows/pr-labeler.yaml

🚧 Files skipped from review as they are similar to previous changes (4)

.github/ISSUE_TEMPLATE/feature_request.md
.github/ISSUE_TEMPLATE/bug_report.md
.github/labels.yml
.github/workflows/pr-labeler.yaml

📝 Walkthrough

Walkthrough

GitHub issue templates now add triage/needs-triage by default, while the repository label definitions and PR labeler mappings were extended for additional areas and scopes.

Changes

GitHub label routing

Layer / File(s)	Summary
Add triage labels to issue templates `.github/ISSUE_TEMPLATE/bug_report.md`, `.github/ISSUE_TEMPLATE/feature_request.md`	Bug and feature request templates now include `triage/needs-triage` in their default labels.
Add new area labels `.github/labels.yml`	Added `area/kamaji`, `area/keycloak`, and `area/tenant` with shared color metadata and descriptions.
Extend scope-to-area mapping `.github/workflows/pr-labeler.yaml`	The PR labeler now maps `mongodb`, `kamaji`, `keycloak`, `csi`, and `tenant` scopes to area labels.

Estimated code review effort: 2 (Simple) | ~10 minutes

Possibly related PRs

cozystack/cozystack#1408: Also updates issue template label front matter.
cozystack/cozystack#3015: Also extends area labels and PR labeler configuration.
cozystack/cozystack#3117: Also modifies PR labeler scope-to-area mappings.

Suggested reviewers: androndo, kvaps, lllamnyp

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title accurately summarizes the main changes: adding needs-triage to new issues and new area labels for keycloak, tenant, and kamaji.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.

✨ Finishing Touches

🧪 Generate unit tests (beta)

Create PR with unit tests
Commit unit tests in branch feat/issue-template-needs-triage-label

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

_{Comment @coderabbitai help to get the list of available commands.}

gemini-code-assist

Code Review

This pull request updates the GitHub issue templates for bug reports and feature requests to include a new 'triage/needs-triage' label. However, the current implementation encloses the comma-separated labels in a single-quoted string, which YAML parsers will interpret as a single literal label. The reviewer correctly identified this issue and provided actionable suggestions to use the proper YAML array format instead.

Important

The consumer version of Gemini Code Assist on GitHub is being sunset. Starting June 18, 2026, new organization installations will be blocked, and all code review activity will officially cease on July 17, 2026.
For more details on the timeline and next steps, please review the Help Documentation.

gemini-code-assist · 2026-07-01T10:36:13Z

 name: Bug report
 about: Create a report to help us improve
-labels: 'kind/bug'
+labels: 'kind/bug, triage/needs-triage'


Enclosing multiple comma-separated labels in single quotes ('kind/bug, triage/needs-triage') causes YAML parsers to treat the entire value as a single string. As a result, GitHub will attempt to apply a single label literally named kind/bug, triage/needs-triage instead of two separate labels.\n\nTo ensure both labels are correctly parsed and applied, use a YAML array format.

Suggested change

labels: 'kind/bug, triage/needs-triage'

labels: ['kind/bug', 'triage/needs-triage']

gemini-code-assist · 2026-07-01T10:36:13Z

 name: Feature request
 about: Propose a concrete, scoped improvement to Cozystack
-labels: 'kind/feature'
+labels: 'kind/feature, triage/needs-triage'


Enclosing multiple comma-separated labels in single quotes ('kind/feature, triage/needs-triage') causes YAML parsers to treat the entire value as a single string. As a result, GitHub will attempt to apply a single label literally named kind/feature, triage/needs-triage instead of two separate labels.\n\nTo ensure both labels are correctly parsed and applied, use a YAML array format.

Suggested change

labels: 'kind/feature, triage/needs-triage'

labels: ['kind/feature', 'triage/needs-triage']

IvanHunters

Approve.

Verified against repo state:

triage/needs-triage exists in labels.yml (frontmatter ref is not dangling)
PR auto-labeler uses exact-key lookup, so the new scope keys (keycloak, tenant, kamaji, mongodb, csi) create no collisions
no duplicate keys in scopeToArea, no duplicate names in labels.yml
new label descriptions are within the 100-char cap, colors are valid hex — the validate job will pass
label sync is additive (delete-other-labels: false), no pruning risk

Pure .github/ change: no cluster upgrade or fresh-install impact.

Every issue created through a template now gets triage/needs-triage so the untriaged backlog is visible at a glance and the stale bot's 60-day clock has a clear signal for maintainers to act on. Assisted-By: Claude <[email protected]> Signed-off-by: Aleksei Sviridkin <[email protected]>

Three scopes recur across PR history with no fitting area/* label (keycloak, tenant, kamaji). Add the labels and map their scopes in the auto-labeler, and fill two gaps in existing mappings (mongodb -> area/database, csi -> area/storage) so these stop landing in area/uncategorized. Assisted-By: Claude <[email protected]> Signed-off-by: Aleksei Sviridkin <[email protected]>

Aleksei Sviridkin (lexfrei) requested review from IvanHunters, Andrey Kolkov (androndo), Andrei Kvapil (kvaps), Timofei Larkin (lllamnyp), myasnikovdaniil and Kirill Ilin (sircthulhu) as code owners July 1, 2026 10:35

github-actions Bot added area/uncategorized PR auto-labeler could not map title scope to a known area/*; please review kind/cleanup Categorizes issue or PR as related to cleanup of code, process, or technical debt labels Jul 1, 2026

github-actions Bot added the size/XS This PR changes 0-9 lines, ignoring generated files label Jul 1, 2026

dosubot Bot added the area/ci Issues or PRs related to CI workflows, GitHub Actions, automation label Jul 1, 2026

gemini-code-assist Bot reviewed Jul 1, 2026

View reviewed changes

github-actions Bot added size/S This PR changes 10-29 lines, ignoring generated files and removed size/XS This PR changes 0-9 lines, ignoring generated files labels Jul 1, 2026

Aleksei Sviridkin (lexfrei) changed the title ~~chore(github): auto-label new issues triage/needs-triage~~ chore(github): needs-triage on new issues + area/{keycloak,tenant,kamaji} labels Jul 1, 2026

Aleksei Sviridkin (lexfrei) self-assigned this Jul 2, 2026

IvanHunters approved these changes Jul 2, 2026

View reviewed changes

Aleksei Sviridkin (lexfrei) added 2 commits July 16, 2026 20:10

Aleksei Sviridkin (lexfrei) force-pushed the feat/issue-template-needs-triage-label branch from 3e9fd75 to 9034206 Compare July 16, 2026 17:11

Aleksei Sviridkin (lexfrei) enabled auto-merge July 16, 2026 17:22

Aleksei Sviridkin (lexfrei) merged commit df541b9 into main Jul 16, 2026
18 checks passed

Aleksei Sviridkin (lexfrei) deleted the feat/issue-template-needs-triage-label branch July 16, 2026 17:59

This was referenced Jul 20, 2026

ci(labeler): map cert-manager, external-secrets and metrics-server scopes #3362

Merged

feat(valkey): add managed Valkey service #3380

Merged

feat(db-autoscaler): implement Database Horizontal Autoscaler operator #3381

Closed

Navigation Menu

Repository navigation

chore(github): needs-triage on new issues + area/{keycloak,tenant,kamaji} labels - #3165

chore(github): needs-triage on new issues + area/{keycloak,tenant,kamaji} labels#3165
Aleksei Sviridkin (lexfrei) merged 2 commits into
mainfrom
feat/issue-template-needs-triage-label

Aleksei Sviridkin (lexfrei) commented Jul 1, 2026 •

edited by coderabbitai Bot

Loading

Uh oh!

gemini-code-assist Bot commented Jul 1, 2026

Uh oh!

coderabbitai Bot commented Jul 1, 2026 •

edited

Loading

Walkthrough

Changes

Uh oh!

gemini-code-assist Bot left a comment

Uh oh!

gemini-code-assist Bot Jul 1, 2026

Uh oh!

gemini-code-assist Bot Jul 1, 2026

Uh oh!

IvanHunters left a comment

Uh oh!

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

2 participants

	labels: 'kind/bug, triage/needs-triage'
	labels: ['kind/bug', 'triage/needs-triage']

	labels: 'kind/feature, triage/needs-triage'
	labels: ['kind/feature', 'triage/needs-triage']

Conversation

Aleksei Sviridkin (lexfrei) commented Jul 1, 2026 • edited by coderabbitai Bot Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

What this PR does

Release note

Summary by CodeRabbit

Uh oh!

gemini-code-assist Bot commented Jul 1, 2026

Summary of Changes

Highlights

Footnotes

Uh oh!

coderabbitai Bot commented Jul 1, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Walkthrough

Changes

Uh oh!

gemini-code-assist Bot left a comment

Choose a reason for hiding this comment

Code Review

Uh oh!

gemini-code-assist Bot Jul 1, 2026

Choose a reason for hiding this comment

Uh oh!

gemini-code-assist Bot Jul 1, 2026

Choose a reason for hiding this comment

Uh oh!

IvanHunters left a comment

Choose a reason for hiding this comment

Uh oh!

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

2 participants

Aleksei Sviridkin (lexfrei) commented Jul 1, 2026 •

edited by coderabbitai Bot

Loading

coderabbitai Bot commented Jul 1, 2026 •

edited

Loading