Every card on the wall is a merged pull request. Built for the DevSphere × FOSS RVU Hacktoberfest meetup at RV University, Bengaluru (23 October 2026).
Live site: link appears here once it's deployed on Vercel
Hacktoberfest/
├── app/ ← the website (you don't need to touch this)
└── profiles/
├── test-user/ ← the example. Copy this folder
│ ├── test_bio.md
│ └── test.jpg
└── your-username/ ← you add this
├── bio.md
└── photo.jpg (optional)
New to Git? That's the whole point of today. Follow along step by step.
- Windows: download the installer from git-scm.com/install/windows and click through it. The defaults are fine. Then open Git Bash.
- macOS: open Terminal and run
git --version. If Git isn't there, macOS offers to install it. Or, with Homebrew:brew install git.
Check it worked:
git --versionClick Fork (top right of this page). You now have your own copy at github.com/YOUR-USERNAME/Hacktoberfest. Clone your fork:
git clone https://github.com/YOUR-USERNAME/Hacktoberfest.git
cd Hacktoberfestcd profiles
cp -r test-user YOUR-USERNAMEYour folder name must be your GitHub username (same spelling). Then open it in your editor:
- Rename
test_bio.mdtobio.mdand write about yourself. - Delete
test.jpgand drop in your own photo (.jpg,.pngor.webp, up to 5 MB). No photo? We'll use your GitHub avatar.
---
name: Samarth
role: AI Engineer @ Hoogway
emoji: 🚀
---
I build AI agents and occasionally break them on purpose.| Field | Required | Limit |
|---|---|---|
name |
yes | 40 characters |
role |
no | 60 characters |
emoji |
no | one emoji |
links |
no | github, linkedin, x, website, instagram (full https:// URLs) |
text under the --- |
yes | 400 characters |
git status
git add .
git commit -m "Add YOUR-USERNAME to the wall"
git push origin mainGo to your fork on GitHub. Click Contribute → Open pull request (or the Compare & pull request button), fill in the template, and click Create pull request.
Then the wall bot takes over:
- ✅ If your folder follows the rules, the bot merges your PR by itself and comments with a link. The site redeploys and you're on the wall in about a minute.
- ❌ If something's off, the bot comments with exactly what to fix. Fix it, commit and push again: the PR updates itself and the bot checks again.
git clone sets everything up for you. For a folder of your own that isn't on GitHub yet, use git init:
git init my-git-project
cd my-git-project
git statusPress . on this repo page to open github.dev (VS Code in your browser). You can create your folder and file there and commit to your fork, then open a PR. Same result, no install.
| You see | Do this |
|---|---|
Support for password authentication was removed |
Run gh auth login, or create a personal access token and use it as the password |
Permission denied / 403 |
You cloned the original repo instead of your fork. Clone github.com/YOUR-USERNAME/Hacktoberfest |
! [rejected] … (fetch first) |
git pull origin main, then push again |
| The check says the folder name is wrong | Rename it to your exact GitHub username: git mv profiles/old profiles/NEW |
Look at the issues labelled good first issue. They're real features for this website (dark mode, filters, a "Surprise me" button…). Comment on one to claim it before you start.
- The site is in
app/and deploys on Vercel with Root Directory =app. Every merge tomainredeploys it. - At build time
app/scripts/collect-profiles.mjsreadsprofiles/, copies photos intopublic/photos/and writessrc/generated/profiles.json. A broken profile is skipped with a warning, so one bad folder never takes the site down. - A profile folder holds one
.mdbio (any name) and at most one photo (any name). An optionalgithub:field links the card to a different GitHub account than the folder name, astest-userdoes. - The wall bot (
.github/workflows/auto-merge.yml+app/scripts/pr-bot.mjs) checks every PR and auto-merges profile PRs that pass:- It runs on
pull_request_target, so it runs straight away even for first-time contributors, using the scripts frommain. It never runs code from the PR: it downloads the PR's profile files through the API as data. - It only merges PRs that touch nothing but
profiles/<PR author>/, and merges exactly the commit it checked. - It rejects bios that try to run code (
---jsfront matter), photos over 5 MB, extra files, and wrong folder names, and comments the fix on the PR. - Words in
.github/blocked-words.txtstop the auto-merge so a human can look. Add aholdlabel to any PR to stop the bot merging it. - PRs that change the site code get a "a maintainer will review this" comment, and
.github/workflows/ci.ymlbuilds them.
- It runs on
- PR timings on the wall: at build time
app/scripts/pr-times.mjsasks the GitHub API when each person's PR was opened and merged (the bot labels those PRswall) and shows it on their card, newest merges first, in IST. If GitHub can't be reached the site still builds, just without timings. On Vercel, optionally add an environment variableGITHUB_TOKEN(a fine-grained token with read-only access to public repos) to raise the API limit from 60 to 5,000 calls an hour. - One-time setup for the bot:
- Settings → Actions → General → Workflow permissions → Read and write permissions.
- Don't add a branch protection rule on
mainthat requires reviews, or the bot can't merge. - Optional: Settings → Secrets and variables → Actions → Variables → add
SITE_URL(your Vercel link) so the bot's comment links to each new card.
- Run locally:
cd app && npm install && npm run dev, then open http://localhost:3000.