Skip to content

Remove validate-quick-start-module workflow and the create-issue step#2081

Merged
atalman merged 1 commit into
pytorch:sitefrom
atalman:quickstart-workflow-cleanup
Jun 12, 2026
Merged

Remove validate-quick-start-module workflow and the create-issue step#2081
atalman merged 1 commit into
pytorch:sitefrom
atalman:quickstart-workflow-cleanup

Conversation

@atalman

@atalman atalman commented Jun 12, 2026

Copy link
Copy Markdown
Contributor

Summary

Two cleanups to the quick start GitHub Actions workflows:

  1. Delete validate-quick-start-module.yml — this validation workflow is no longer needed here.

Validation is done here: https://github.com/pytorch/test-infra/blob/main/.github/workflows/validate-binaries.yml after every RC, before and after the Release

  1. Remove the "Create Issue if failed" step from update-quick-start-module.yml.

Why remove the create-issue step

The step used dacbd/create-issue-action@main and passed it secrets.PYTORCHBOT_TOKEN:

- name: Create Issue if failed
  uses: dacbd/create-issue-action@main
  if: ${{ failure() }}
  with:
    token: ${{secrets.PYTORCHBOT_TOKEN}}

This is a supply-chain exposure:

  • The action is pinned to a mutable @main ref, so any future (or compromised) commit runs in our job.
  • It receives a long-lived broad PAT (PYTORCHBOT_TOKEN), far more privileged than opening an issue requires. A malicious version could exfiltrate it; the pytorchbot-env environment gates release of the secret but does not stop the third-party action from reading it once the job runs.

Since the failure is already visible from the scheduled run's status, the step isn't needed — removing it is the simplest fix and eliminates the exposure. The Create Pull Request step is unchanged (it legitimately needs a PAT so the PR triggers CI).

This PR was authored with the assistance of an AI coding assistant.

Two cleanups to the quick start workflows:

- Delete .github/workflows/validate-quick-start-module.yml. The validation is
  no longer needed here.

- Drop the "Create Issue if failed" step from update-quick-start-module.yml.
  It used dacbd/create-issue-action@main -- an unpinned third-party action
  pinned to a mutable branch -- and handed it the long-lived PYTORCHBOT_TOKEN
  PAT, which is broader than issue creation needs. Removing the step is the
  simplest fix and eliminates the supply-chain exposure; the workflow's
  failure is still visible from the scheduled run's status.

This PR was authored with the assistance of an AI coding assistant.
@netlify

netlify Bot commented Jun 12, 2026

Copy link
Copy Markdown

Deploy Preview for pytorch-dot-org-preview ready!

Name Link
🔨 Latest commit ec681d2
🔍 Latest deploy log https://app.netlify.com/projects/pytorch-dot-org-preview/deploys/6a2c18b80ed88c0007b2186b
😎 Deploy Preview https://deploy-preview-2081--pytorch-dot-org-preview.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.

To edit notification comments on pull requests, go to your Netlify project configuration.

@albanD albanD left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Ok!

@atalman atalman merged commit 8056186 into pytorch:site Jun 12, 2026
9 of 13 checks passed
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