yarnpkg / yarnpkg/berry

[Case Study] GitHub Actions

Open
#343 2 comments 2 reactions 1 assignee View on GitHub

@arcanis is already working on this.

Since Aug 9, 2019.

case study
Dominant language
TypeScript
Stars
8.1k
Forks
1.3k
PR merge metrics
No merged PRs in 30d

Description

What package is covered by this investigations?

GitHub Actions

Describe the goal of the investigation

Now that the GitHub Actions support CI systems, we should figure out which actions the yarnpkg org should provide that would help maintaining our projects.

Investigation report

The following actions look interesting:

  • An action that setup the right Yarn binary (or just shell out to the local build if no version is provided in the local variables).

  • A "sanity check action" that ensures that the PR is in a valid state against master (no added / modified files when running install, no removed files when running cache clean, ...)

Any more ideas?

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.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.