Skip to content

disable potentially vulnerable workflow#3664

Merged
ahpook merged 1 commit into
mainfrom
ahpook/disable-jekyll
May 14, 2026
Merged

disable potentially vulnerable workflow#3664
ahpook merged 1 commit into
mainfrom
ahpook/disable-jekyll

Conversation

@ahpook
Copy link
Copy Markdown
Contributor

@ahpook ahpook commented May 14, 2026

  • Have you followed the contributing guidelines?
  • Have you explained what your changes do, and why they add value to the Guides?

Please note: we will close your PR without comment if you do not check the boxes above and provide ALL requested information.


@ahpook ahpook requested a review from a team as a code owner May 14, 2026 16:14
Copilot AI review requested due to automatic review settings May 14, 2026 16:14
@ahpook ahpook temporarily deployed to Pages Preview May 14, 2026 16:15 — with GitHub Actions Inactive
@ahpook ahpook merged commit e43eeaf into main May 14, 2026
9 checks passed
@ahpook ahpook deleted the ahpook/disable-jekyll branch May 14, 2026 16:16
Copy link
Copy Markdown
Contributor

Copilot AI left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

This PR disables the GitHub Actions workflow that deploys a Jekyll site to a GitHub Pages preview environment, likely to mitigate risk associated with the current PR-targeted deployment approach.

Changes:

  • Comments out the entire .github/workflows/jekyll-preview.yml workflow so it no longer defines triggers/jobs.
  • Effectively removes the Pages preview build/deploy pipeline from CI.
Show a summary per file
File Description
.github/workflows/jekyll-preview.yml Entire workflow content is commented out to prevent Pages preview deployments from running.

Copilot's findings

Tip

Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

  • Files reviewed: 1/1 changed files
  • Comments generated: 2

Comment on lines +1 to +65
# # This workflow uses actions that are not certified by GitHub.
# # They are provided by a third-party and are governed by
# # separate terms of service, privacy policy, and support
# # documentation.
#
# # Sample workflow for building and deploying a Jekyll site to GitHub Pages
# name: Deploy Jekyll site to Pages preview environment
# on:
# # Runs on pull requests targeting the default branch
# pull_request_target:
# branches: ["main"]
# # Sets permissions of the GITHUB_TOKEN to allow deployment to GitHub Pages
# permissions:
# contents: read
# pages: write
# id-token: write
# # Allow only one concurrent deployment per PR, skipping runs queued between the run in-progress and latest queued.
# # However, do NOT cancel in-progress runs as we want to allow these production deployments to complete.
# concurrency:
# group: "pages-preview @ ${{ github.event.pull_request.head.label || github.head_ref || github.ref }}"
# cancel-in-progress: false
# jobs:
# # Build job
# build:
# environment:
# name: "Pages Preview"
# # Limit permissions of the GITHUB_TOKEN for untrusted code
# permissions:
# contents: read
# runs-on: ubuntu-latest
# steps:
# - name: Checkout
# uses: actions/checkout@v6.0.2
# with:
# # For PRs make sure to checkout the PR branch
# ref: ${{ github.event.pull_request.head.sha }}
# repository: ${{ github.event.pull_request.head.repo.full_name }}
# - name: Setup Pages
# uses: actions/configure-pages@v6.0.0
# - name: Build with Jekyll
# uses: actions/jekyll-build-pages@44a6e6beabd48582f863aeeb6cb2151cc1716697 # v1
# with:
# source: ./
# destination: ./_site
# - name: Upload artifact
# # Automatically uploads an artifact from the './_site' directory by default
# uses: actions/upload-pages-artifact@v5.0.0
# # Deployment job
# deploy:
# environment:
# name: "Pages Preview"
# url: ${{ steps.deployment.outputs.page_url }}
# # Sets permissions of the GITHUB_TOKEN to allow deployment to GitHub Pages
# permissions:
# contents: read
# pages: write
# id-token: write
# runs-on: ubuntu-latest
# needs: build
# steps:
# - name: Deploy to GitHub Pages
# id: deployment
# uses: actions/deploy-pages@v5.0.0
# with:
# preview: "true"
Comment on lines +1 to +18
# # This workflow uses actions that are not certified by GitHub.
# # They are provided by a third-party and are governed by
# # separate terms of service, privacy policy, and support
# # documentation.
#
# # Sample workflow for building and deploying a Jekyll site to GitHub Pages
# name: Deploy Jekyll site to Pages preview environment
# on:
# # Runs on pull requests targeting the default branch
# pull_request_target:
# branches: ["main"]
# # Sets permissions of the GITHUB_TOKEN to allow deployment to GitHub Pages
# permissions:
# contents: read
# pages: write
# id-token: write
# # Allow only one concurrent deployment per PR, skipping runs queued between the run in-progress and latest queued.
# # However, do NOT cancel in-progress runs as we want to allow these production deployments to complete.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants