My Resume Builder

Builds DOCX, PDF, and HTML artifacts from a resume in markdown format. Automated with Pandoc and implemented with Github Actions.

Usage

The current config assumes that the resume within the repository is named resume.md. When pushing an update to the repository, the resume is automatically built and then committed to the repo within the output directory. The output files use the name of the repository owner.

Note: This behavior can be adjusted in the workflow yaml file.

Github Actions Repository Requirements

In order for the runner to have the permissions needed to push commits, the repository must have it's workflow permssions set to read/write.

Github Actions Workflow

name: My Resume Builder
run-name: My Resume Builder (${{ github.repository_owner }})
on:
  push:
    branches:
      - main
  pull_request:
    branches:
      - main
jobs:
  convert-via-pandoc:
    env:
      RESUME_NAME: ${{ github.repository_owner }}
      RESUME_MARKDOWN: resume.md
      RESUME_OUT_DIR: output
      GIT_COMMIT_MESSAGE: Continuous Integration Build Artifacts
    runs-on: ubuntu-latest
    steps:
      - name: Check out repository code
        uses: actions/checkout@v5

      - name: Validate output directory
        run: mkdir -p ${{ env.RESUME_OUT_DIR }}

      - name: Build DOCX
        uses: docker://pandoc/core:3.8
        with:
          args: >-
            --standalone
            --reference-doc=templates/reference.docx
            --output=${{ env.RESUME_OUT_DIR }}/${{ env.RESUME_NAME }}.docx
            ${{ env.RESUME_MARKDOWN }}

      - name: Build HTML
        uses: docker://pandoc/core:3.8
        with:
          args: >-
            --standalone
            --template=templates/reference.html
            --output=${{ env.RESUME_OUT_DIR }}/${{ env.RESUME_NAME }}.html
            ${{ env.RESUME_MARKDOWN }}

      - name: Build PDF
        uses: docker://pandoc/extra:3.8
        with:
          args: >-
            --standalone
            --template=/.pandoc/templates/eisvogel.latex
            --output=${{ env.RESUME_OUT_DIR }}/${{ env.RESUME_NAME }}.pdf
            ${{ env.RESUME_MARKDOWN }}

      - name: GIT Commit Build Artifacts
        if: github.event_name == 'push'
        run: |
          git config --global user.name "github-actions[bot]"
          git config --global user.email "41898282+github-actions[bot]@users.noreply.github.com"
          git add ${{ env.RESUME_OUT_DIR }}
          git commit -m "${{ env.GIT_COMMIT_MESSAGE }}"
          git push

Local Build

Environment Setup

To test the build locally, you will need a working installation of Pandoc, LaTeX, and the Eisvogel template.

# install pandoc (mac os)
brew install pandoc

# install latex (mac os)
brew install mactex

# install eisvogel templates
wget https://github.com/Wandmalfarbe/pandoc-latex-template/releases/download/v3.2.1/Eisvogel.zip
unzip Eisvogel.zip
mkdir -p ~/.pandoc/templates
cp ./Eisvogel-3.2.1/eisvogel.* ~/.pandoc/templates
rm -rf ./Eisvogel-3.2.1

# install git-filter-repo for refresh.sh support (mac)
brew install git-filter-repo

Document Generation

Example 1 (manual):

# docx
pandoc resume.md -s -o output/johnd.docx --reference-doc=reference.docx

# pdf
pandoc resume.md -s -o output/johnd.pdf  --template=eisvogel

# html
pandoc resume.md -s -o output/johnd.html --template=templates/reference.html

Example 2 (using build script):

./build.sh johnd

Github Actions Testing

You can do local CI testing with nektoact.

Example:

act --container-architecture linux/amd64

Reference

• Pandoc Documentation
• LATeX Installation
• Eisvogel LaTeX Template
• Most effective ways to push within GitHub Actions (via Johtizen)
• Using Github Actions with Pandoc (via Pandoc)

License

The MIT License (MIT)

Copyright (c) 2026 Nicholas Marus <nmarus@gmail.com>

Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:

The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.

THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.