Skip to content

Fix Bundler version conflict by using explicit path to new Bundler #8

Fix Bundler version conflict by using explicit path to new Bundler

Fix Bundler version conflict by using explicit path to new Bundler #8

name: Deploy to GitHub Pages
on:
push:
branches: [ main ]
workflow_dispatch:
permissions:
contents: read
pages: write
id-token: write
concurrency:
group: "pages"
cancel-in-progress: false
jobs:
# Build job
build:
runs-on: ubuntu-latest
steps:
- name: Checkout
uses: actions/checkout@v4
- name: Setup Pages
uses: actions/configure-pages@v4
- name: Setup Ruby
uses: ruby/setup-ruby@v1
with:
ruby-version: '3.2'
bundler-cache: false
working-directory: www
- name: Build with Jekyll
run: |
cd www
gem install bundler -v "~> 2.6"
# Use the full path to the new bundler to avoid using the pre-installed one
$(which bundle) --version
$(which bundle) install
$(which bundle) exec jekyll build
env:
JEKYLL_ENV: production
- name: Upload artifact
uses: actions/upload-pages-artifact@v3
with:
path: www/_site
# Deployment job
deploy:
environment:
name: github-pages
url: ${{ steps.deployment.outputs.page_url }}
runs-on: ubuntu-latest
needs: build
steps:
- name: Deploy to GitHub Pages
id: deployment
uses: actions/deploy-pages@v4