Add workflow to route issues to team board by dkastl · Pull Request #58 · geolonia/.github

dkastl · 2026-06-12T00:21:13Z

This workflow routes issues to the team board based on field changes.

Summary by CodeRabbit

Chores
- Added automation to route issue field changes to the appropriate team board.
- Ensures required dispatch secrets are forwarded so routing runs reliably and preserves expected department-routing behavior.

This workflow routes issues to the team board based on field changes.

coderabbitai · 2026-06-12T00:21:25Z

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: ASSERTIVE

Plan: Pro

Run ID: 2681be56-6703-4352-9dad-6b6dd1c11d68

📥 Commits

Reviewing files that changed from the base of the PR and between 77464f3 and a1a6669.

📒 Files selected for processing (1)

.github/workflows/route-issue.yml

Walkthrough

Adds a new GitHub Actions workflow that triggers on issue field changes (field_added, field_removed) and delegates routing logic to a shared reusable workflow from the geolonia organization with inherited secrets.

Changes

Issue routing workflow

Layer / File(s)	Summary
Route issue workflow trigger and job `.github/workflows/route-issue.yml`	Workflow triggers on issue field add/remove events with read-only `contents` permission, and a single `route` job calls the pinned `reusable-route-issue.yml` workflow while forwarding repository secrets (`secrets: inherit`).

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~10 minutes

Possibly related issues

geolonia/geolonia-backstage#207: Adds the same route-issue.yml caller that pins and delegates to the reusable-route-issue workflow.
geolonia/geolonia-operations#156: Adds a public-facing route-issue.yml that forwards Department field changes to the pinned reusable workflow for routing to org project boards.
Add reusable workflow: route tagged issues to team boards (public dispatch leg) #56: Related main issue describing the public dispatch leg and caller workflow that invokes the reusable routing logic.

Possibly related PRs

geolonia/.github#57: Introduces the reusable-route-issue.yml reusable workflow that this PR's new workflow delegates to.

🚥 Pre-merge checks | ✅ 4 | ❌ 1

❌ Failed checks (1 inconclusive)

Check name	Status	Explanation	Resolution
Description check	❓ Inconclusive	The description provided is minimal and lacks structured information matching the template requirements (Summary, Checklist, Related Issues sections).	Expand the description to follow the template structure by adding details about what the workflow does, checking relevant boxes, and linking any related issues.

✅ Passed checks (4 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title clearly and concisely summarizes the main change: adding a GitHub Actions workflow that routes issues to a team board.
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.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing Touches

🧪 Generate unit tests (beta)

Create PR with unit tests
Commit unit tests in branch dkastl-patch-2

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

github-actions · 2026-06-12T00:21:28Z

Secret Leak Check

OK No secrets detected in this PR's diff.

coderabbitai

Actionable comments posted: 2

🤖 Prompt for all review comments with AI agents

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

Inline comments:
In @.github/workflows/route-issue.yml:
- Line 13: Replace the blanket "secrets: inherit" usage in the reusable workflow
call with an explicit secrets mapping that only passes OPS_DISPATCH_CLIENT_ID
and OPS_DISPATCH_APP_PRIVATE_KEY from the repository secrets into the reusable
workflow; remove "secrets: inherit" and add a secrets block that maps each
required secret name to the corresponding repository secret to enforce
least-privilege.
- Line 12: Replace the mutable tag reference in the workflow invocation string
"uses: geolonia/.github/.github/workflows/reusable-route-issue.yml@v1" with the
exact commit SHA recommended by static analysis (e.g., change "`@v1`" to
"@<commit-sha>") so the reusable workflow is pinned to an immutable commit;
update the single line that contains that uses: entry and commit the change.

🪄 Autofix (Beta)

Fix all unresolved CodeRabbit comments on this PR:

Push a commit to this branch (recommended)
Create a new PR with the fixes

ℹ️ Review info

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: ASSERTIVE

Plan: Pro

Run ID: eabd4543-c1e5-448f-8224-05c4694f3dc3

📥 Commits

Reviewing files that changed from the base of the PR and between 92c8c6d and 77464f3.

📒 Files selected for processing (1)

.github/workflows/route-issue.yml

coderabbitai · 2026-06-12T00:24:19Z

+jobs:
+  route:
+    uses: geolonia/.github/.github/workflows/reusable-route-issue.yml@v1
+    secrets: inherit


🧹 Nitpick | 🔵 Trivial | 💤 Low value

Consider explicit secret passing for improved security posture.

While secrets: inherit is convenient and works correctly for this workflow, it passes all repository secrets to the reusable workflow. The reusable workflow requires only OPS_DISPATCH_CLIENT_ID and OPS_DISPATCH_APP_PRIVATE_KEY secrets.

For better least-privilege security, consider explicitly listing only the required secrets:

🛡️ Optional improvement for explicit secret passing

- secrets: inherit + secrets: + OPS_DISPATCH_CLIENT_ID: ${{ secrets.OPS_DISPATCH_CLIENT_ID }} + OPS_DISPATCH_APP_PRIVATE_KEY: ${{ secrets.OPS_DISPATCH_APP_PRIVATE_KEY }}

📝 Committable suggestion

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

Suggested change

secrets: inherit

secrets:

OPS_DISPATCH_CLIENT_ID: ${{ secrets.OPS_DISPATCH_CLIENT_ID }}

OPS_DISPATCH_APP_PRIVATE_KEY: ${{ secrets.OPS_DISPATCH_APP_PRIVATE_KEY }}

🤖 Prompt for AI Agents

Verify each finding against current code. Fix only still-valid issues, skip the rest with a brief reason, keep changes minimal, and validate. In @.github/workflows/route-issue.yml at line 13, Replace the blanket "secrets: inherit" usage in the reusable workflow call with an explicit secrets mapping that only passes OPS_DISPATCH_CLIENT_ID and OPS_DISPATCH_APP_PRIVATE_KEY from the repository secrets into the reusable workflow; remove "secrets: inherit" and add a secrets block that maps each required secret name to the corresponding repository secret to enforce least-privilege.

Source: Linters/SAST tools

Updated the reusable workflow reference to a specific commit hash for version 1.16.0.

github-actions · 2026-06-12T00:26:34Z

Secret Leak Check

OK No secrets detected in this PR's diff.

Add workflow to route issues to team board

77464f3

This workflow routes issues to the team board based on field changes.

coderabbitai Bot reviewed Jun 12, 2026

View reviewed changes

Update reusable-route-issue workflow reference

a1a6669

Updated the reusable workflow reference to a specific commit hash for version 1.16.0.

dkastl merged commit a0dda21 into main Jun 12, 2026
3 checks passed

dkastl deleted the dkastl-patch-2 branch June 12, 2026 00:33

coderabbitai Bot mentioned this pull request Jun 12, 2026

docs(route-issue): simplify page, picker description + template comments #61

Merged

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Add workflow to route issues to team board#58

Add workflow to route issues to team board#58
dkastl merged 2 commits into
mainfrom
dkastl-patch-2

dkastl commented Jun 12, 2026 •

edited by coderabbitai Bot

Loading

Uh oh!

coderabbitai Bot commented Jun 12, 2026 •

edited

Loading

❌ Failed checks (1 inconclusive)

Uh oh!

github-actions Bot commented Jun 12, 2026

Uh oh!

coderabbitai Bot left a comment

Uh oh!

Uh oh!

coderabbitai Bot Jun 12, 2026

Uh oh!

github-actions Bot commented Jun 12, 2026

Uh oh!

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

1 participant

Conversation

dkastl commented Jun 12, 2026 • edited by coderabbitai Bot Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Summary by CodeRabbit

Uh oh!

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

Uh oh!

Walkthrough

Changes

Estimated code review effort

Possibly related issues

Possibly related PRs

❌ Failed checks (1 inconclusive)

Uh oh!

github-actions Bot commented Jun 12, 2026

Secret Leak Check

Uh oh!

coderabbitai Bot left a comment

Choose a reason for hiding this comment

Uh oh!

Uh oh!

coderabbitai Bot Jun 12, 2026

Choose a reason for hiding this comment

Uh oh!

github-actions Bot commented Jun 12, 2026

Secret Leak Check

Uh oh!

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

1 participant

dkastl commented Jun 12, 2026 •

edited by coderabbitai Bot

Loading

coderabbitai Bot commented Jun 12, 2026 •

edited

Loading