Introduce automation to keep `pnpm/action-setup` up-to-date

Open Beginner friendly
#169 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
68/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Active
Tech stack
github-actions
Domain
ci-cd, devops

Research direction

Start by searching the repository's workflow files for references to pnpm/action-setup and compare them with the Apache GitHub Actions policy. Update the workflows to use a hash-pinned action and add automation such as Dependabot to keep it current. Done means the repository complies with the policy and future updates are automated.

Written by the indexing model from the issue text.

Description

Hello! This issue was created semi-automatically because this repo popped up in a search. Per https://infra.apache.org/github-actions-policy.html, 3rd-party actions such as pnpm/action-setup must be referred to by hash and kept up-to-date by automation such as dependabot. It looks like this repo does not pollow this policy yet.

We plan to start enforcing this policy for pnpm/action-setup through https://github.com/apache/infrastructure-actions/pull/1193 .

If this was a false posivite, you can close this issue. Otherwise, you likely want to update your workflows, since they will stop working once that PR is merged.

Dominant language
Jupyter Notebook
Stars
30
Forks
15
PR merge metrics
No merged PRs in 30d

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 apache/flagon

All issues in apache/flagon

Similar issues

More DevOps issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.