-
Notifications
You must be signed in to change notification settings - Fork 6
[32] Add GitHub Actions CI for StepFi-API #16
Copy link
Copy link
Closed
Labels
GrantFox OSSIssue tracked in GrantFox OSSIssue tracked in GrantFox OSSMaybe RewardedIssue may be eligible for a GrantFox rewardIssue may be eligible for a GrantFox rewardOfficial CampaignCampaign: Official CampaignCampaign: Official Campaigncidevopsgood first issueGood for newcomersGood for newcomers
Metadata
Metadata
Assignees
Labels
GrantFox OSSIssue tracked in GrantFox OSSIssue tracked in GrantFox OSSMaybe RewardedIssue may be eligible for a GrantFox rewardIssue may be eligible for a GrantFox rewardOfficial CampaignCampaign: Official CampaignCampaign: Official Campaigncidevopsgood first issueGood for newcomersGood for newcomers
Type
Fields
Give feedbackNo fields configured for issues without a type.
Problem
The StepFi-API repo has no GitHub Actions workflow. PRs can merge with broken TypeScript builds or failing tests because nothing enforces them.
Context
Open-source contributors will submit PRs blind. CI is the gate that prevents broken builds from landing in main. Without it, the maintainer has to manually run
npm run buildon every PR.Before Starting
Read these context files first:
What To Build
.github/workflows/ci.yml.pull_requestto main +pushto main.build-test: ubuntu-latest, Node 20 viaactions/setup-node@v4withcache: 'npm'.npm ci→npm run build→npm test.node_moduleskeyed onpackage-lock.jsonhash.Files To Touch
.github/workflows/ci.ymlREADME.mdAcceptance Criteria
Mandatory Checks Before PR