아직 감지된 업데이트가 없습니다. GitHub 릴리스가 나오면 여기에 보입니다.
최근 완료된 8시간 회차 사이 GitHub 스타 증가량 순
Use Zwift Click, Zwift Play, Shimano Di2, or any Bluetooth controller with MyWhoosh, Rouvy, Zwift, and more. Free to try on iOS, Android, Windows, and macOS.
개인 계정의 공개 저장소 소유자는 GitHub로 로그인해 운영자를 확인하고 소개를 직접 관리할 수 있습니다. 관리자 승인은 필요하지 않습니다.
로그인한 뒤 확인 파일을 만들어 이 저장소의 기본 브랜치에 30분 안에 커밋해 주세요. 다른 브랜치나 포크의 파일은 인정하지 않습니다. 파일을 올린 뒤 아래에서 확인하면 관리자 승인 없이 관리할 수 있습니다. 자격을 유지하려면 파일을 남겨 두세요.
로그인이 필요하면 로그인 화면으로 이동합니다. 로그인 후 이곳으로 돌아와 원하는 확인 버튼을 다시 눌러 주세요.
프로젝트 폴더에서 /nomorevibe verify를 실행하면 소유권을 확인하고 소개를 직접 관리할 수 있습니다.
1분 만에 확인하기App to track all of the group wagers for CFB/NFL
저장소 README에서 가져옴
README 전체를 불러오는 중입니다. 아래는 저장된 발췌입니다.
A private web app for a friend group's weekly football betting league. Members submit picks on college football and NFL games each week, compete on a live leaderboard, and track performance over a full season.README 전문 보기 ↗A private web app for a friend group's weekly football betting league. Members submit picks on college football and NFL games each week, compete on a live leaderboard, and track performance over a full season.
A lock's weight is its weight in games as well as in points — the league reads the record, not the point total, so a lock has to show up in the W‑L.
| Result | Regular Pick | Lock of the Week | Lock of the Year |
|---|---|---|---|
| Win | +1 · 1 W | +2 · 2 W | +7 · 7 W |
| Push | 0 · 1 P | 0 · 1 P | 0 · 1 P |
| Loss | −1 · 1 L | −2 · 2 L | −7 · 7 L |
So a member who goes 2–3 on the week with the LOTW among the losses reads 2–4; with the LOTY among them, 2–9. A push is a no‑action and stays one row however it was locked.
One lock per week, one LOTY per season. A LOTY stands in place of that week's LOTW rather than sitting beside it — spend it in week 4 and you have no separate LOTW that week.
Forfeit penalty: −1 point per pick slot not filled by week close (e.g., if 10 picks are required and you submit 8, you lose 2 points).
LOTW missing penalty: −1 point if no Lock of the Week is designated before the week closes.
| Layer | Tool | Why |
|---|---|---|
| Frontend | Next.js 14+ | React framework, works as a mobile PWA, includes API routes |
| Database & Auth | Supabase | Postgres, magic link login, real-time updates, row-level security |
| Schedule sync | Python script (GitHub Actions) | Pulls CFB + NFL schedules weekly from free public APIs |
| Deployment | Vercel | Zero-config Next.js hosting, free tier |
External APIs (free):
betting-site/
├── openspec/
│ └── changes/
│ └── betting-tracker/
│ ├── proposal.md # What we're building and why
│ └── specs/
│ ├── member-auth/ # Login, roles, invites
│ ├── game-schedule-sync/ # API schedule pull
│ ├── pick-entry/ # Member pick submission
│ ├── pick-visibility/ # Blind picks + admin override
│ ├── scoring-engine/ # Point rules, forfeits, LOTW
│ ├── result-resolution/ # Admin enters game results
│ ├── leaderboard/ # Weekly + season standings
│ ├── historical-analytics/# All-time stats and trends
│ └── admin-management/ # Week setup, close-out, invites
└── README.md
Day 1 (this build):
Day 2 (planned):
The full behavioral specs for every feature live in openspec/changes/betting-tracker/specs/. Read those before writing any code — they define exactly what the system must do, including edge cases and admin workflows. The proposal at openspec/changes/betting-tracker/proposal.md explains the overall scope and the decisions made during planning.