ci: repo has no GitHub Actions workflow, so pushes and pull requests are never built or tested

Open Beginner friendly
#7 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
74/100
Issue type
Feature
Clarity
Clearly specified
Activity status
Active
Tech stack
github-actions, javascript
Domain
ci-cd

Research direction

Start by reading package.json to find the install, build, lint and test scripts the workflow must call, then look at the sibling flisk-sh repos' workflow files under .github/workflows to copy their shape. Add one workflow in .github/workflows triggered on push and pull_request, running the discovered commands on Node. Done means a pull request with a deliberate break shows a failing check, and the reverted branch goes green.

Written by the indexing model from the issue text.

Description

agents area: runtime automation chore cli consistency dependencies developer-experience difficulty: easy documentation enhancement good first issue help wanted hygiene json-output priority: P3 starters tests

Problem

The repository has code but no GitHub Actions workflow. Pull requests and pushes run no build, test or lint, so a broken change can land on the default branch unnoticed, and contributors get no signal that their change works. Other Flisk repos run CI on every push.

Reproduce:

  1. Open the repository and look for a workflows folder under the GitHub config directory.
  2. There is none, and the Actions tab shows "Get started with GitHub Actions".
  3. Open any pull request: no checks are listed.

Expected: one workflow that installs dependencies and runs the project's build and tests (or at least a start-and-health-check) on every push and pull request.

Root Cause Analysis

The repo was set up without a workflow and nothing in the org requires one. Without a required check, nothing stops a regression from reaching the default branch, and the repo's current state is unverified.

TDD Fix Plan

  1. RED: Open a pull request that deliberately breaks the build and observe that no check fails.
    GREEN: Add a workflow that builds and tests on push and pull request, and confirm the same pull request now shows a red check.

  2. RED: Remove the broken change and confirm the check is still red until fixed.
    GREEN: Revert the break and confirm the check turns green.

REFACTOR: Reuse the org's shared workflow or the same steps as the sibling repos.

Acceptance Criteria

  • A workflow runs on every push and pull request
  • A deliberately broken change fails the check
  • The default branch passes
  • All new tests pass
  • Existing tests still pass
Dominant language
JavaScript
Stars
0
Forks
2
Avg merge
1h 33m
Merged PRs (30d)
7

Getting set up

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 flisk-sh/analytics

All issues in flisk-sh/analytics

Similar issues

More JavaScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.