knative / knative/actions

[EPIC] Processify reusable GHAs groundwork

Open
#62 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
No language data
Stars
11
Forks
25
Avg merge
2d 18h
Merged PRs (30d)
3

Description

Since the introduction of reusable actions and other improvements to Github Actions in general, some order, process, and migrations need to be done.

To set up the ground work to retire/migrate knobots over the following proposal of work can be done:

  1. Provide a standard naming convention and directory layout for future actions
  1. Make reusables enable-able via configuration
  1. Switch over to new changes

The end result should allow repo owners to subscribe to which actions they would like to use. Ensure all reusables for repos to stay in sync and provide a standard way to add future actions.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reviewing the unchecked linked issues 49, 50, 59, 61, and 66, since this epic does not name files, tests, or a single entry point. Done means the listed naming, configuration, and migration work is complete, with repository owners able to subscribe to the reusable actions and repos staying in sync.

Written by the indexing model from the issue text.

Assessment

Tech stack
github-actions
Domain
ci-cd
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
20/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.