GitHub - sadigaxund/git-resume · GitHub

/" data-turbo-transient="true" />

Skip to content

Search or jump to...

Search code, repositories, users, issues, pull requests...

-->

Search

Clear

Search syntax tips

Provide feedback

--><br>We read every piece of feedback, and take your input very seriously.

Include my email address so I can be contacted

Cancel

Submit feedback

Saved searches

Use saved searches to filter your results more quickly

-->

Name

Query

To see all available qualifiers, see our documentation.

Cancel

Create saved search

Sign in

/;ref_cta:Sign up;ref_loc:header logged out"}"<br>Sign up

Appearance settings

Resetting focus

You signed in with another tab or window. Reload to refresh your session.<br>You signed out in another tab or window. Reload to refresh your session.<br>You switched accounts on another tab or window. Reload to refresh your session.

Dismiss alert

{{ message }}

sadigaxund

git-resume

Public

Notifications<br>You must be signed in to change notification settings

Fork

Star

main

BranchesTags

Go to file

CodeOpen more actions menu

Folders and files<br>NameNameLast commit message<br>Last commit date<br>Latest commit

History<br>11 Commits<br>11 Commits

.github/workflows

.github/workflows

skills

skills

template

template

.gitignore

.gitignore

AGENTS.md

AGENTS.md

README.md

README.md

View all files

Repository files navigation

Fork it. Push a .tex. Get versioned PDFs + a live viewer — automatically.

git-resume

Fork it, edit and generate your resume from template/, push. GitHub Actions compiles it, cuts a release with the PDF attached, and updates a hosted page where you can browse every version you've pushed. See Demo.

Setup

Fork and clone this repo

Replace the .tex file in template/ with your own, and drop any logos into template/icons/

Edit template/resume.yml:<br>variant: general<br>label: General<br>author: "Your Name"<br>template: "YourResume.tex"<br>output: "YourName_Resume" # optional, defaults to the .tex filename

Set your name inside the .tex file itself — it's hardcoded in the header, so resume.yml's author field won't change it for you

Push to main

NOTE: Turn on Pages once (Settings → Pages → Source: GitHub Actions) — this is a one-time manual step, per repo . Forks don't inherit this setting; each fork owner must enable it themselves.

What happens on push

One workflow handles all of it:

Compiles template/*.tex with XeLaTeX (needed for the bundled fonts — plain pdflatex won't render them)

Publishes the PDF as a release: a latest- tag that always points at the newest build, plus a dated resume--YYYY-MM-DD tag whenever the content actually changes

Rebuilds the GitHub Pages viewer, which reads the release list and lets you flip between every version you've published

See it in action: sadigaxund.github.io/git-resume — two-level profile/version selector, renders PDFs inline in your browser.

Nothing is committed back to the repo. The PDF and the site are build output, not history you have to manage by hand.

Different resumes for different applications

main is your default resume. If you want a different version for a specific application — say a data-engineering-flavored resume for one company — create a branch named resume/, e.g. resume/facebook-de, with its own resume.yml:

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

Push it, and it builds and releases on its own — separate tags, separate entry in the viewer's profile dropdown. 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. Check skills/ first — it holds optional writing guidance (ATS-friendliness, tone, this template's macros) meant to be read before any content gets touched, by a human or an agent. Swap in your own style guide there if you want different rules.

Layout

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

License

Fork it and use it for your own resume.

About<br>No description, website, or topics provided.<br>Resources<br>Readme<br>Activity<br>Stars<br>1 star<br>Watchers<br>0 watching<br>Forks<br>1 fork<br>Report repository

Releases

Packages

Contributors

Languages

You can’t perform that action at this time.