Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Improve Github Action Workflow

Open
  • Is something wrong?
#29 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
48/100
Issue type
Refactor
Clarity
Clearly specified
Activity status
Stale
Tech stack
github-actions, node.js
Domain
build-system, ci-cd, devops

Research direction

Open .github/workflows/checks.yml and compare the unchecked items with the existing workflow on the develop branch. Verify the test and build job relationship, update the remaining command and naming items, add the requested header comments, and confirm the workflow configuration is valid.

Written by the indexing model from the issue text.

Description

@danielfdsilva spent time in #24 improving the GitHub workflow.
To keep our git history clean and make reviews easier, we should extract the workflow improvements into their own PR, based on the develop branch.

GitHub Actions Workflow Updates (.github/workflows/checks.yml)

  • Add descriptive header comments explaining the workflow purpose
  • Update trigger conditions:
    • Remove push trigger on main branch
    • Update pull_request types to: opened, synchronize, reopened, ready_for_review
    • Add concurrency controls to cancel in-progress runs for the same ref
  • Update Node.js version strategy:
    • Remove hardcoded NODE environment variable
    • Use node-version-file: '.nvmrc' to read version from .nvmrc file
  • Update GitHub Actions to latest versions:
    • actions/checkout@v2 → actions/checkout@v4
    • actions/setup-node@v1 → actions/setup-node@v4
    • actions/cache@v2 → actions/cache@v4
    • Remove deprecated styfle/cancel-workflow-action (replaced by concurrency)
  • Simplify cache key:
    • Remove cache-name environment variable
    • Use ${{ runner.os }}-build-${{ hashFiles('**/package.json') }}
  • Update job commands:
    • Use explicit yarn run lint instead of yarn lint
    • Use explicit yarn run test instead of yarn test
    • Use explicit yarn run build instead of yarn build
    • Fix build job step name: "Test" → "Build"
  • Ensure build job depends on test job (not changed, but verify)

References

  • Original PR: #24
  • Target branch: develop

Notes

This is purely infrastructure/tooling changes with no functional code changes to the library itself.

Dominant language
TypeScript
Stars
34
Forks
4
No merged PRs in 30d

Getting set up

This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.

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 developmentseed/stac-react

All issues in developmentseed/stac-react

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.