Skip to content

Disable GitHub Actions workflows (org-wide enablement migration)#536

Merged
eredi93 merged 1 commit into
mainfrom
eredi93/disable-actions-workflows
Jun 3, 2026
Merged

Disable GitHub Actions workflows (org-wide enablement migration)#536
eredi93 merged 1 commit into
mainfrom
eredi93/disable-actions-workflows

Conversation

@eredi93

@eredi93 eredi93 commented Jun 2, 2026

Copy link
Copy Markdown
Member

Why?

As part of an org-wide GitHub Actions enablement migration, workflow files are being moved to .github/workflows-disabled/ to prevent them from triggering automatically until each workflow has been reviewed and approved for production use.

How?

All 8 workflow files are relocated from .github/workflows/ to .github/workflows-disabled/ — no workflow logic is changed. To re-enable a specific workflow later, move its file back into .github/workflows/ following the standard re-enable safety review.

Generated with Claude Code

Move .github/workflows/*.yml(.yaml) to .github/workflows-disabled/ to neutralize
them ahead of the org-wide GitHub Actions enablement. Restore via the
re-enable-workflow process when a workflow is intentionally re-enabled.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
@eredi93 eredi93 self-assigned this Jun 2, 2026

@normprovost normprovost left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

Verified: pure rename of .github/workflows -> .github/workflows-disabled (8 files, no content changes). Auto-approved.

@eredi93
eredi93 merged commit fce5a62 into main Jun 3, 2026
2 checks passed
@eredi93
eredi93 deleted the eredi93/disable-actions-workflows branch June 3, 2026 18:05
zilleeizad-inter added a commit that referenced this pull request Jul 23, 2026
The CI/CD table describes intended behavior, but `.github/workflows/`
doesn't exist on main — every workflow moved to `workflows-disabled/`
as part of PR #536 (org-wide GitHub Actions enablement migration,
2026-06-03), and FERN_TOKEN / FERN_NPM_TOKEN were removed after the
2026-05-01 Fern token incident. Restoration is a separate operation
gated on both the org migration and secret re-provisioning.

Adds a leading note above the table so readers know the schedule
column is aspirational until re-enablement.
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