https://github.com/alessbell/resume

LaTeX source of my resume 📜
https://github.com/alessbell/resume

latex resume

Last synced: 11 days ago
JSON representation

LaTeX source of my resume 📜

• Host: GitHub
• URL: https://github.com/alessbell/resume
• Owner: alessbell
• Created: 2019-06-02T19:12:54.000Z (over 5 years ago)
• Default Branch: main
• Last Pushed: 2024-08-18T12:26:33.000Z (3 months ago)
• Last Synced: 2024-10-11T12:56:26.691Z (27 days ago)
• Topics: latex, resume
• Language: TeX
• Homepage: https://aless.co/resume.pdf
• Size: 26.4 KB
• Stars: 3
• Watchers: 3
• Forks: 2
• Open Issues: 1
• Metadata Files:
  • Readme: README.md

Awesome Lists containing this project

README

        
# resume!

Inspired by [`dcousineau/resume`](https://github.com/dcousineau/resume) -- especially the clever strategy of using `releases` as an archive of various "built" states over time.

If you're on a mac, `brew cask install mactex && pdflatex resume.tex`

# automated releases

As of October 2019, I've automated the process for generating GitHub releases of new versions of my resume.

First, I compile a new `resume.pdf` using this excellent [LaTeX Action](https://github.com/xu-cheng/latex-action) which uses `pdfLaTeX` under the hood. Then I use the [GH Release action](https://github.com/marketplace/actions/gh-release) to upload the newly-generated `resume.pdf` as a release asset. 🎉

Finally, I kick off a GitHub Action in my blog's repo, [`alessbell/aless.co`](https://github.com/alessbell/aless.co), and open a PR with the PDF release asset from the latest release. I've written more about how I've automated this flow [here](https://aless.co/resume-as-code/).

# steps to publish

1. Cut a branch, make some changes and add a new commit. Then run e.g. `git tag -a v1.4 -m "Release v1.4, adds new job"` and create a PR.

2. Push local tags up with `git push origin --tags`. This will kick off the GitHub action. After it succeeds, merge the pull request.⚡️