crickets-and-comb/shared

Replace all third-party actions with in-house actions or reusable workflows.

Open

#37 opened on Mar 22, 2025

View on GitHub
 (0 comments) (0 reactions) (0 assignees)Makefile (0 forks)auto 404
enhancementhelp wanted

Repository metrics

Stars
 (2 stars)
PR merge metrics
 (PR metrics pending)

Description

We use a handful of third-party actions in our shared and repo-specific workflows. Some of them require us to pass along keys, tokens, permissions, etc. Also, we become dependent on them not releasing a breaking change to the version we've pinned to.

Ideally, we would write our own actions and workflows. Some may even be replaced with simple shell scripts.

We should:

  1. Catalog the actions we use.
  2. Identify how vulnerable each makes us.
  3. Estimate how simple it would be to replace them.
  4. Begin replacing them starting with the highest risk and easiest to replace.

Contributor guide

Research direction
Catalog all third party actions used in shared workflows, assess their security vulnerabilities and ease of replacement, and begin replacing them starting with the highest risk and easiest to replace.
Tech stack
shellgithub actions
Domain
ci cd
Issue type
Refactor
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
3-5 days
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
GitGitHub Actions
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
60