alex/.profile
Watch
1
0
Fork
You've already forked .profile
 0
Code Issues 1 Pull requests Projects 1 Activity Actions

Add label to dashboard #6

New issue
Closed
opened 2026-07-01 11:41:49 +00:00 by alex · 2 comments
alex commented 2026-07-01 11:41:49 +00:00
Owner
Copy link
No description provided.
alex commented 2026-07-01 11:42:40 +00:00
Author
Owner
Copy link

/pi see if it's possible to add lables to the Dependency dashboard issues created by renovate, if so patch in a new pr

/pi see if it's possible to add lables to the Dependency dashboard issues created by renovate, if so patch in a new pr
forgejo-actions commented 2026-07-01 11:47:30 +00:00
Copy link

I'll investigate the current Renovate configuration to understand how the Dependency Dashboard works and how labels can be added.The renovate.json is currently minimal with only the schema reference. Let me verify the exact Renovate configuration option for dashboard labels by checking the official schema.The dependencyDashboardLabels option exists in the Renovate schema. Let me get the full details on this option to confirm its type and behavior.The dependencyDashboardLabels option is confirmed in the official schema. It accepts an array of strings and applies them to the Dependency Dashboard issue. Now let me check the current git state and PR #6's branch.Let me look at the CI workflow and check existing labels in the repo to decide on appropriate label naming.Let me check the existing labels available in this repository so I use a label that exists.No labels exist in the repo yet. Let me check for organization-level and default labels available in Forgejo.The repository has no labels yet. For dependencyDashboardLabels to actually work, the referenced label must exist (Renovate can only apply existing labels, it cannot create them).

Here's my finding: Yes, it is possible — Renovate provides the dependencyDashboardLabels option, an array of strings that are always applied to the Dependency Dashboard issue (re-applied even if removed manually).

Let me now make the changes. First, I'll create the label via the API so the config is immediately functional, then patch renovate.json.The dependencies label now exists. Now let me update renovate.json to enable the dashboard explicitly and apply the label.The config is valid. Now let me create the new PR as requested.PR creation via the tool failed with a 404. Let me create the branch and PR manually via git and the Forgejo API.Branch pushed. Now let me create the PR via the Forgejo API.PR #7 created. Let me verify it looks correct.Done. Here's the summary:

✅ Yes — it's possible, and it's now patched in PR #7

Renovate has a dedicated, first-class option for this:

  • dependencyDashboardLabels — an array of strings that are always applied to the Dependency Dashboard issue, and re-applied even if someone removes them manually.

This is deliberately separate from the generic labels option (which tags every PR/issue Renovate opens), so it scopes the label to the dashboard issue only.

The change (renovate.json):

 {
   "$schema": "https://docs.renovatebot.com/renovate-schema.json",
+  "dependencyDashboard": true,
+  "dependencyDashboardLabels": ["dependencies"]
 }

One important caveat: Renovate can only apply labels that already exist on the platform — it can't create them, so without the label present the option silently no-ops. Since labels are repo metadata (not in git), I created the dependencies label directly via the API (#0366d6) so the feature works as soon as this merges. If you'd rather use a different name/color, say the word and I'll adjust both the config and the label.

PR #7 is open and mergeable.

View action run | Model: zai/glm-5.2 (thinking: xhigh) | Time: 4m 50s | Tokens: 167.7K | Pi SDK v0.80.3 | Action v2.25.0-develop (develop @ 0e171ae)

I'll investigate the current Renovate configuration to understand how the Dependency Dashboard works and how labels can be added.The `renovate.json` is currently minimal with only the schema reference. Let me verify the exact Renovate configuration option for dashboard labels by checking the official schema.The `dependencyDashboardLabels` option exists in the Renovate schema. Let me get the full details on this option to confirm its type and behavior.The `dependencyDashboardLabels` option is confirmed in the official schema. It accepts an array of strings and applies them to the Dependency Dashboard issue. Now let me check the current git state and PR #6's branch.Let me look at the CI workflow and check existing labels in the repo to decide on appropriate label naming.Let me check the existing labels available in this repository so I use a label that exists.No labels exist in the repo yet. Let me check for organization-level and default labels available in Forgejo.The repository has no labels yet. For `dependencyDashboardLabels` to actually work, the referenced label must exist (Renovate can only apply existing labels, it cannot create them). Here's my finding: **Yes, it is possible** — Renovate provides the [`dependencyDashboardLabels`](https://docs.renovatebot.com/configuration-options/#dependencydashboardlabels) option, an array of strings that are always applied to the Dependency Dashboard issue (re-applied even if removed manually). Let me now make the changes. First, I'll create the label via the API so the config is immediately functional, then patch `renovate.json`.The `dependencies` label now exists. Now let me update `renovate.json` to enable the dashboard explicitly and apply the label.The config is valid. Now let me create the new PR as requested.PR creation via the tool failed with a 404. Let me create the branch and PR manually via git and the Forgejo API.Branch pushed. Now let me create the PR via the Forgejo API.PR #7 created. Let me verify it looks correct.Done. Here's the summary: ## ✅ Yes — it's possible, and it's now patched in **[PR #7](https://forge.l3x.in/alex/.profile/pulls/7)** Renovate has a dedicated, first-class option for this: - **[`dependencyDashboardLabels`](https://docs.renovatebot.com/configuration-options/#dependencydashboardlabels)** — an array of strings that are **always applied to the Dependency Dashboard issue**, and re-applied even if someone removes them manually. This is deliberately separate from the generic `labels` option (which tags *every* PR/issue Renovate opens), so it scopes the label to the dashboard issue only. **The change (`renovate.json`):** ```diff { "$schema": "https://docs.renovatebot.com/renovate-schema.json", + "dependencyDashboard": true, + "dependencyDashboardLabels": ["dependencies"] } ``` **One important caveat:** Renovate can only *apply* labels that already exist on the platform — it can't create them, so without the label present the option silently no-ops. Since labels are repo metadata (not in git), I created the `dependencies` label directly via the API (`#0366d6`) so the feature works as soon as this merges. If you'd rather use a different name/color, say the word and I'll adjust both the config and the label. PR #7 is open and mergeable. --- [View action run](https://forge.l3x.in/alex/.profile/actions/runs/7) | Model: zai/glm-5.2 (thinking: xhigh) | Time: 4m 50s | Tokens: 167.7K | Pi SDK v0.80.3 | Action v2.25.0-develop (develop @ 0e171ae)
alex closed this issue 2026-07-01 12:00:47 +00:00
Sign in to join this conversation.
No Branch/Tag specified
Branches Tags
master
No results found.
Labels
Clear labels   
dependencies
Renovate stuff

No labels
dependencies
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
2 participants
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
alex/.profile#6
No description provided.