docs: route archived repo links to oss-archive snapshots#68
Conversation
Made-with: Cursor
✅ Deploy Preview for ianalloway ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
Made-with: Cursor
There was a problem hiding this comment.
Pull request overview
Routes links that previously pointed to archived standalone repositories to their equivalent oss-archive/tree/archive/<repo> snapshots, keeping the portfolio’s project references accurate while preserving links to still-active repos.
Changes:
- Updated archived GitHub repository links across the portfolio landing page and hire page.
- Updated the projects list component to point archived project “GitHub” and “demo/README” links to
oss-archivesnapshots. - Updated the sports ML case study HTML and employer outreach template to reference the archived snapshot links.
Reviewed changes
Copilot reviewed 6 out of 6 changed files in this pull request and generated 1 comment.
Show a summary per file
| File | Description |
|---|---|
| src/pages/Index.tsx | Repoints featured/selected project repo links to oss-archive snapshot paths. |
| src/pages/HireMe.tsx | Updates featured work repo links to oss-archive snapshot paths. |
| src/components/Projects.tsx | Updates project github + README demo links for archived repos to oss-archive snapshot paths. |
| public/papers/sports-ml-evaluation-case-study.html | Updates case study “Links” section to point archived repos at oss-archive. |
| docs/employer-pack/outreach-ten-touches.md | Updates outreach template’s flagship repo reference to the archived snapshot path. |
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
| | 7 | Consult prospect | Angel / portco operator intro | Warm or semi-warm | Portfolio ops | Hi {{NAME}} — for portcos sitting on prediction products, I’ve published the same eval pattern I’d use on a diligence or build sprint: https://ianalloway.xyz/papers/sports-ml-evaluation-case-study.html Happy to be a bench resource for data-heavy checks. | | ||
| | 8 | Referral | {{MUTUAL}} introduction double opt-in | Email | Double opt-in | {{NAME}} — would you be okay if I reached out to {{CONTACT}} at {{COMPANY}} about ML/eval work? I’ll keep it short; background: https://ianalloway.xyz/papers/sports-ml-evaluation-case-study.html | | ||
| | 9 | Hiring manager | Recruiter follow-up after app | Email | Application + artifact | Hi — I applied for {{ROLE}} (ref # if any). Attaching context: one-pager on my sports ML eval stack (https://ianalloway.xyz/papers/sports-ml-evaluation-case-study.html). GitHub flagship: github.com/ianalloway/nba-clv-dashboard. Happy to walk through live. | | ||
| | 9 | Hiring manager | Recruiter follow-up after app | Email | Application + artifact | Hi — I applied for {{ROLE}} (ref # if any). Attaching context: one-pager on my sports ML eval stack (https://ianalloway.xyz/papers/sports-ml-evaluation-case-study.html). GitHub flagship: github.com/ianalloway/oss-archive/tree/archive/nba-clv-dashboard. Happy to walk through live. | |
There was a problem hiding this comment.
Row #9 uses a bare github.com/... URL without a scheme, which many Markdown renderers won’t auto-link (and it’s inconsistent with the surrounding https:// URLs). Use the full https://github.com/ianalloway/oss-archive/tree/archive/nba-clv-dashboard form (or wrap in <...> to force autolinking).
| | 9 | Hiring manager | Recruiter follow-up after app | Email | Application + artifact | Hi — I applied for {{ROLE}} (ref # if any). Attaching context: one-pager on my sports ML eval stack (https://ianalloway.xyz/papers/sports-ml-evaluation-case-study.html). GitHub flagship: github.com/ianalloway/oss-archive/tree/archive/nba-clv-dashboard. Happy to walk through live. | | |
| | 9 | Hiring manager | Recruiter follow-up after app | Email | Application + artifact | Hi — I applied for {{ROLE}} (ref # if any). Attaching context: one-pager on my sports ML eval stack (https://ianalloway.xyz/papers/sports-ml-evaluation-case-study.html). GitHub flagship: https://github.com/ianalloway/oss-archive/tree/archive/nba-clv-dashboard. Happy to walk through live. | |
![devin-ai-integration[bot]](https://avatars.githubusercontent.com/in/811515?s=60&v=4){kind=small}
| label: 'All public repositories', | ||
| href: 'https://github.com/ianalloway?tab=repositories&q=&sort=updated', | ||
| note: '8 active + archived read-only · sorted by updated', | ||
| note: '9 active + archived read-only · sorted by updated', |
There was a problem hiding this comment.
🟡 AGENTS.md changelog not updated from 8 → 9 active repos after adding ai-sports-monorepo
The AGENTS.md changelog entry explicitly states /toolkit lists 8 active public repos. This PR adds ai-sports-monorepo to CORE_SECTION in src/pages/Toolkit.tsx and updates all user-facing text to say "nine" / "9", but AGENTS.md (AGENTS.md:7) was not updated to reflect the new count. The AGENTS.md "Useful Links" section at line 57 designates Toolkit.tsx (CORE_SECTION + START_HERE) as the authoritative public repo catalog that "matches profile 'featured' story", and the changelog instructs maintainers to "Sync profile README + Toolkit." Leaving AGENTS.md at 8 while the code says 9 violates that sync requirement.
Prompt for agents
The PR updates the active repo count from 8 to 9 across Toolkit.tsx (lines 46, 62, 207) and adds ai-sports-monorepo to CORE_SECTION (lines 75-79), but AGENTS.md line 7 still says 8 active public repos. Update the AGENTS.md changelog entry to say 9 active repos (or add a new changelog row for the current date reflecting the addition of ai-sports-monorepo). The relevant AGENTS.md section is the table at line 5-7.
Was this helpful? React with 👍 or 👎 to provide feedback.
| title: 'Active public repositories', | ||
| blurb: | ||
| 'Eight non-archived repos on this account. Dozens of additional projects were merged into branch-per-repo snapshots under oss-archive before archiving the originals read-only.', | ||
| 'Nine non-archived repos on this account. Dozens of additional projects were merged into branch-per-repo snapshots under oss-archive before archiving the originals read-only.', |
There was a problem hiding this comment.
🟡 JSDoc comment above CORE_SECTION still says "(8)" after count changed to 9
The comment on src/pages/Toolkit.tsx:57 reads /** Active public repos (8). ... */ but the PR added ai-sports-monorepo as a 9th row to CORE_SECTION.rows and updated all user-facing strings (blurb, START_HERE note, header) to say "Nine" / "9". The source comment was missed in the transformation, leaving a stale count that will mislead future maintainers.
Prompt for agents
Update the JSDoc comment on Toolkit.tsx line 57 from Active public repos (8) to Active public repos (9) to match the actual CORE_SECTION.rows length after adding ai-sports-monorepo. The comment is: /** Active public repos (8). Older OSS lives on frozen branches in oss-archive. */
Was this helpful? React with 👍 or 👎 to provide feedback.
Summary
oss-archive/tree/archive/<repo>linksai-advantage,sports-betting-ml,kelly-js,nba-ratings)Test plan
npm run buildpasses locallysrc/,public/, and docs searchedMade with Cursor