chore: delete retired GitHub Actions/Depot workflows

Merged
YA
4d ago
+0-107

User description

GitHub Actions is retired for good and Buildkite is this repo's CI (pipeline buildkite/api-spec, the only required check on main).

This deletes the dead workflow below and nothing else. It's part of the GH_PACKAGES_READ_TOKEN retirement after the s03 exposure: the workflow writes an npm.pkg.github.com npmrc, and that path is being replaced by registry.wave-ci.internal.

Deleted:

  • .github/workflows/governance-enforce.yml (not a required status check; the governance gate runs on Buildkite)

No other files are touched (dependabot.yml left alone). Draft: do not merge without Orchestrator's go-ahead.

Refs: WAVE-28266


CodeAnt-AI Description

Remove the retired GitHub Actions governance workflow

What Changed

  • Pull requests, pushes to the main branches, and merge-queue events no longer start this GitHub Actions scan for secrets and hardcoded paths.
  • Governance enforcement and required CI checks remain on Buildkite.

Impact

✅ No GitHub Actions runs for governance scanning
✅ Governance checks stay on Buildkite
✅ No GitHub Packages token needed for this workflow

💡 Usage Guide

Checking Your Pull Request

Every time you make a pull request, our system automatically looks through it. We check for security issues, mistakes in how you're setting up your infrastructure, and common code problems. We do this to make sure your changes are solid and won't cause any trouble later.

Talking to CodeAnt AI

Got a question or need a hand with something in your pull request? You can easily get in touch with CodeAnt AI right here. Just type the following in a comment on your pull request, and replace "Your question here" with whatever you want to ask:

@codeant-ai ask: Your question here

This lets you have a chat with CodeAnt AI about your pull request, making it easier to understand and improve your code.

Example

@codeant-ai ask: Can you suggest a safer alternative to storing this secret?

Preserve Org Learnings with CodeAnt

You can record team preferences so CodeAnt AI applies them in future reviews. Reply directly to the specific CodeAnt AI suggestion (in the same thread) and replace "Your feedback here" with your input:

@codeant-ai: Your feedback here

This helps CodeAnt AI learn and adapt to your team's coding style and standards.

Example

@codeant-ai: Do not flag unused imports.

Retrigger review

Ask CodeAnt AI to review the PR again, by typing:

@codeant-ai: review

Check Your Repository Health

To analyze the health of your code repository, visit our dashboard at https://app.codeant.ai. This tool helps you identify potential issues and areas for improvement in your codebase, ensuring your repository maintains high standards of code health.

[!NOTE]

Remove retired governance-enforce GitHub Actions workflow

Deletes governance-enforce.yml in full. This removes the enforce job that ran on pull requests, merge queue, and main/master pushes. Risk: the A_BLOCK governance enforcement no longer runs from this workflow, so check whether another mechanism now covers it.

Macroscope summarized 7061731.