Repository navigation
chore: delete retired GitHub Actions/Depot workflows - #121
Merged
Merged
Conversation
GitHub Actions is retired; Buildkite is CI. Part of the GH_PACKAGES_READ_TOKEN retirement after the s03 exposure.
🤖 CodeAnt AI — Review Status
|
Thanks for using CodeAnt! 🎉We're free for open-source projects. if you're enjoying it, help us grow by sharing. Share on X · |
CodeAnt PR Risk: Low Risk
Assessed commit: |
There was a problem hiding this comment.
No issues found across 1 file
Confidence score: 5/5
- Automated review surfaced no issues in the provided summaries.
- No files require special attention.
Architecture diagram
sequenceDiagram
participant Dev as Developer
participant GH as GitHub
participant BK as Buildkite
participant Reg as registry.wave-ci.internal
participant Gov as Governance Enforcer (@wave-av/governance)
Note over Dev,GH: CI/CD Pipeline for api-spec Repository
Dev->>GH: Push to main / open PR / merge queue
GH->>BK: Trigger buildkite/api-spec pipeline
alt Required CI checks on main
BK->>BK: Run CI pipeline
BK-->>GH: Report check status
end
Note over GH,BK: Governance Gate (Buildkite-hosted)
BK->>Reg: Fetch governance enforcer package
Reg-->>BK: @wave-av/governance@0.4.6
BK->>Gov: Execute enforce.mjs --changed BASE
Gov->>Gov: Scan diff for secrets & hardcoded paths
Gov-->>BK: Enforcement results (PASS/FAIL)
BK-->>GH: Report governance check status
Note over GH,Gov: GitHub Actions retired - no longer runs governance scans
Note over Dev,GH: GH_PACKAGES_READ_TOKEN no longer needed for workflow
Note over Reg: npm.pkg.github.com registry path replaced
🟢 WAVE BugBot — clearNo confident findings on the changed lines. Local review · $0 inference · wave-dispatch |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
User description
GitHub Actions is retired for good and Buildkite is this repo's CI (pipeline
buildkite/api-spec, the only required check onmain).This deletes the dead workflow below and nothing else. It's part of the
GH_PACKAGES_READ_TOKENretirement after the s03 exposure: the workflow writes annpm.pkg.github.comnpmrc, and that path is being replaced byregistry.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.ymlleft 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
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:
This lets you have a chat with CodeAnt AI about your pull request, making it easier to understand and improve your code.
Example
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:
This helps CodeAnt AI learn and adapt to your team's coding style and standards.
Example
Retrigger review
Ask CodeAnt AI to review the PR again, by typing:
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-enforceGitHub Actions workflowDeletes governance-enforce.yml in full. This removes the
enforcejob 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.