Repository navigation
chore(ci): delete the workflows that build and deploy the blog (ENG-2000) - #39
Open
lucas-koontz wants to merge 1 commit into
Open
lucas-koontz wants to merge 1 commit into
lucas-koontz wants to merge 1 commit into
Conversation
Delete the only two workflows in this repository. dev-build-deploy-on-main.yaml ran on every push to main. It built the blog image and helm-installed every chart under deployment/ into the dev namespace. prod-build-deploy-on-release.yaml ran on a published release or a manual dispatch, and did the same into the prod namespace. Both workflows ran on the mdb-dev and mdb-prod self-hosted runners. GitHub recommends GitHub-hosted runners for public repositories, but moving these jobs there would keep deploying a blog that no public URL reaches. mindsdb.com/blog now redirects to https://mindshub.ai/blog, a site this repository does not build. The last deploys ran on 2025-06-04 (dev) and 2025-02-13 (prod). With no workflow on main, a push to main or a manual dispatch starts no job. The charts under deployment/ and the Dockerfile stay. Their READMEs describe a manual helm install, which this change leaves as it is. Part of Lucas Koontz's ticket "Take the public repos off the credentialed runner group and require devops to release a privileged run". Refs: ENG-2000
This was referenced Oct 4, 2026
Draft
This branch has not been deployed
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 story
As a maintainer of this repository
I want
mainto hold no workflow that builds or deploys the old blogSo that a push to
mainor a manual dispatch starts no job on a self-hosted runnerWhy this matters
A maintainer who merges to
maintoday rebuilds the blog image and redeploys its charts into thedevnamespace, and a published release does the same inprod. No reader sees either deploy, becausehttps://mindsdb.com/blogredirects tohttps://mindshub.ai/blog, a site this repository does not build. Both workflows run on self-hosted runners, and GitHub recommends GitHub-hosted runners for public repositories. Moving the jobs to GitHub-hosted runners would only keep an unused deploy alive, so this PR deletes both workflows.Test plan
mainhas no.githubdirectory, and the push the merge makes starts no workflow run.mindsdb/github-actionsor either deleted workflow..github/workflows/changes.deployment/, theDockerfileand both chart READMEs stay as they are.Part of ENG-2000. This PR depends on no other change.