knative / knative/actions

Enforce reusable GHA naming convention

Open
#49 1 comment 0 reactions 0 assignees View on GitHub
Dominant language
No language data
Stars
11
Forks
25
Avg merge
2d 18h
Merged PRs (30d)
3

Description

Need a GHA to enforce that anyone adding a reusable GHA should have it prefixed with `reusable_` this is needed because of a limitation of GHAs where composite actions can live in their own repo (and that should be enforced as well), but reusable workflows have to live in the same repo as other workflows. This is very confusing for people so this naming convention will help people differentiate between what is a local workflow vs a reusable one.

Contributor guide

Open the contributing guide

Research direction

No files or tests are named. Start by inspecting the repository's GitHub Actions configuration and how reusable workflows and composite actions are represented, then identify where an automated naming check would run. Done means the check distinguishes reusable workflows from other workflows and enforces the `reusable_` prefix, including the stated composite-action case.

Written by the indexing model from the issue text.

Assessment

Tech stack
github-actions
Domain
ci-cd
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
45/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.