A tiny release pipeline for your resume — push a change, keep every version.

git-resume

git-resume is a small release pipeline for your resume. You edit a LaTeX file and push; CI compiles it, publishes a latest-<variant> release plus dated snapshots, and rebuilds a hosted viewer, so every version you've pushed stays one click away. You write the resume. The repo handles the workflow.

git push → CI compile → release (latest + dated tags) → live viewer

Live demo: as-foss.github.io/git-resume · demo video

Quick start

1. Hit Use this template or fork, then clone your copy. Want it private? See Public or private?.
2. Put your resume in template/: replace the .tex and drop any logos into template/icons/.
3. Edit template/resume.yml:

   variant: general
   label: General
   author: "Your Name"
   template: "YourResume.tex"
   output: "YourName_Resume"   # optional

4. Set your name in the .tex file. It's hardcoded in the header; resume.yml won't change it.
5. Push to main.

Note

Enable Pages once per repo: Settings → Pages → Source: GitHub Actions. Your copy won't have it on by default.

Privacy

Forking keeps you in the fork network, so you can pull updates from this repo. For a private copy, use Use this template instead. Two trade-offs: you leave the fork network (no more updates from this repo), and GitHub Pages needs a paid plan (Pro or higher) on private repositories.

Variants

One branch, one resume. main is your default; resume/<role> is a tailored version for one application. Each branch carries its own resume.yml:

variant: facebook-de
label: Facebook Data Engineer
author: "Your Name"
template: "Resume.tex"
output: "YourName_Facebook_DE"

Push the branch and it builds on its own, with its own tags and its own entry in the viewer. Editing one variant never touches another.

Editing with AI

You don't have to write LaTeX by hand. Point a free coding agent like opencode at the repo and ask it to update your resume. Read skills/ first: it holds optional writing guidance (ATS-friendliness, tone, template macros) for humans and agents alike. Swap in your own style guide if you want different rules.

Layout

template/
  *.tex           resume content, compiled with XeLaTeX
  resume.yml      variant, label, author, template, output filename
  fonts/          font files, must stay next to the .tex
  icons/          logos referenced from the .tex
  index.html      source for the Pages viewer
skills/           optional content-writing guidance, not read by CI
.github/workflows/build-resume.yml   the whole pipeline