Harden GitHub Actions workflows

Open
#225 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
48/100
Issue type
Refactor
Clarity
Mostly clear
Activity status
Quiet
Tech stack
github-actions
Domain
ci-cd, devops, security

Research direction

Start by inspecting the repository's GitHub Actions workflow files and compare the requested work with processing/p5.js#9033 and pull request 9032. Done means existing dependencies are pinned, an automatic update mechanism is configured, and zizmor-reported best-practice fixes are applied across the workflows.

Written by the indexing model from the issue text.

Description

Parallel to https://github.com/processing/p5.js/issues/9033, I believe all repos under processing organization needs the same base level of hardening for CI pipepilines.

The work will be done in multiple parts:

  • Initial pinning of existing dependencies - similar to https://github.com/processing/p5.js/pull/9032
  • Configuring an auto update mechanism, preferably with Renovate
  • Enforcing best practices with zizmor and applying the missing fixes
Dominant language
Rust
Stars
69
Forks
14
Avg merge
15d 22h
Merged PRs (30d)
3

Contributor guide

No contributing guide indexed for this repository

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.

More from processing/libprocessing

All issues in processing/libprocessing

Similar issues

More Rust issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.