Skip to content

SenSei2121/interview-test

Folders and files

NameName
Last commit message
Last commit date

Latest commit

Β 

History

4 Commits
Β 
Β 
Β 
Β 
Β 
Β 

Repository files navigation

πŸ“¦ Sentari Kit

This folder contains everything a candidate needs to complete an interview task.

Tech stack: Next.js 15 (App Router, React Server Components) React 19 TypeScript Tailwind CSS 3 Supabase

Structure:

contrib/
 β”œβ”€ README.md                # you are here
 β”œβ”€ template/                # minimal repo candidates will fork
 └─ scripts/
     └─ verify-contrib.sh    # maintainer helper to check a submission

Read template/README.md for the instructions you will send to candidates.

Folder structure

contrib/
 β”œβ”€ README.md                # this guide
 β”œβ”€ template/                # minimal project template for contributors
 β”‚   β”œβ”€ src/
 β”‚   β”‚   β”œβ”€ lib/
 β”‚   β”‚   β”‚   └─ sampleService.ts
 β”‚   β”‚   └─ app/api/sample/route.ts
 β”‚   β”œβ”€ tests/
 β”‚   β”‚   └─ sample.test.ts
 β”‚   β”œβ”€ package.json         # locked dependency versions
 β”‚   β”œβ”€ tsconfig.json
 β”‚   └─ .eslintrc.json
 └─ scripts/
     └─ verify-contrib.sh    # one-liner acceptance script for maintainers

Quick workflow overview

  1. A contributor forks the template/ repo (or clicks Use this template on GitHub).
  2. They implement their feature following template/README.md and make sure pnpm lint && pnpm test are both green.
  3. They generate a patch.diff or simply share the repository URL in the designated Issue.
  4. You run scripts/verify-contrib.sh <repo-url> to clone the repo and execute the automated checks offline.
  5. If it passes and looks valuable, you manually cherry-pick / copy the code into the main code-base.

Important: everything lives under the contrib/ sub-directory

About

No description, website, or topics provided.

Resources

Stars

Watchers

Forks

Releases

No releases published

Packages

No packages published

Contributors 2

  •  
  •