fix(workflow-templates): use GitHub-recognized categories#30
Merged
Conversation
The workflow-template UI in github.com/new only renders a category badge for categories from the recognized set (Automation, Code scanning, Continuous integration, Deployment, Pages). "Security" and "Documentation" silently produce no badge. - secret-leak-check: Security -> Code scanning - publish-techdocs: Documentation -> Deployment Display names now match the others (CDK Deploy Monitor, Geolonia Release, Sync Team Access).
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Path: .coderabbit.yaml Review profile: ASSERTIVE Plan: Pro Run ID: 📒 Files selected for processing (2)
WalkthroughThis PR updates workflow template categorization metadata in two configuration files. The "Publish Backstage TechDocs" template moves from Documentation to Deployment, while the secret leak checker moves from Security to Code scanning. Both changes are single-line category field updates in JSON property files. ChangesWorkflow Template Categories
🎯 1 (Trivial) | ⏱️ ~2 minutes 🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches🧪 Generate unit tests (beta)
Comment |
2 tasks
dkastl
added a commit
that referenced
this pull request
May 19, 2026
…gating (#37) Setting the category to `Code scanning` in a workflow-template's properties.json file makes GitHub mark the template as "Requires GitHub Advanced Security" in the New Workflow picker (visible on private repos without a GHAS license). The secret leak scanner here does not depend on GHAS at all -- it runs betterleaks in a regular ubuntu-latest job and posts plain GitHub Actions annotations -- so the gating banner is misleading and discourages adoption. Switch to `Automation`, which renders a badge in the picker (matching Geolonia Release and Sync Team Access) and has no feature gating. Regression from #30.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Both Publish Backstage TechDocs and Secret Leak Check (per PR) had `categories` defined, but GitHub's workflow-template UI silently dropped the badge because the values were not in the recognized set.
The recognized set per actions/starter-workflows is: Automation, Code scanning, Continuous integration, Deployment, Pages.
Test plan
Summary by CodeRabbit