Automate Resume Deployment with GitHub Actions
Over the past weekend a took up a bit of a project I was not expecting, using Github Actions for building and deploying my Resume! I love programming and when I came across LateX, I knew I want to use it for building my resume. The advantages that motivated me were the ability to use Git versioning, which would allow me to track changes, and the opportunity to write code instead of dealing with clunky Word files.
Previously, I would update my resume, export it as a PDF, and upload it to Google Drive and update my Bento. This process was tedious and prone to version control issues. I wanted a streamlined, automated way to generate and deploy my resume.
My initial plan was to set up GitHub Actions to build the LaTeX resume and automatically create a release. This would allow me to download the PDF from GitHub whenever I needed it. However, as I configured GitHub Actions, I realized I could also deploy my resume directly to GitHub Pages. This meant that my resume would always be available online, with a permanent URL that stays updated whenever I push changes—no more manually uploading to Drive!
By using GitHub Pages, I now have a single, static URL for my resume that is always up to date. This means I can share the link with anyone and be sure they have the latest version of my resume. I love automation!
