Repository navigation
Conversation
Add the four wrappers the service repos use to run the weekly staging -> main release: the Friday freeze, the release PR, the unfreeze when that PR merges, and the main -> staging sync after any other push to main. Each calls the shared reusable in mindsdb/github-actions. The release PR wrapper fires on the freeze alone. mindshub has no staging deploy pipeline to refresh it mid-week, so that trigger is dropped from the copy. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Contributor
Author
|
Closed in favor of merging PRs directly to main |
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.
Description
Adds mindshub to the weekly staging → main release, the same process the service repos use:
staging.stagingwhen the release PR merges, then syncsmainback into it.mainintostagingafter any other push to main, such as a hotfix.Each file is a small wrapper around a shared workflow in mindsdb/github-actions, copied from scratchpad-controller. There's one real change: the release PR job runs only after the freeze. The service repos also refresh it after each staging deploy, but mindshub has no staging deploy. Use workflow_dispatch to see what's queued mid-week.
After this merges, work goes to
stagingand reachesmainonce a week. Docs changes count too, becausedeploy_docs.ymlpublishes frommain. Urgent docs fixes can still go straight tomainas hotfixes; the sync carries them back to staging.Merge order:
stagingalready containsmain.staging_frozenproperty tofalse. Until that's done, every one of these workflows fails and posts an alert to Slack.main. Scheduled triggers only run from the default branch.Type of change
Verification Process
Test Location: Specify the URL or path for testing.
Verification Steps: Outline the steps or queries needed to validate the change. Include any data, configurations, or actions required to reproduce or see the new functionality.
python3 scripts/workflow_graph.py --workflow-dir <mindshub>/.github/workflows(from github-actions): the new workflows add no errors. It reports one error that was already there:codeql.ymlanddeploy_docs.ymlboth run on push tomain. This PR leaves that alone.All workflow YAML parses.
Not run: the workflows themselves. They can't run until the admin setup is done. After merging: run Staging Freeze by hand, check that a push to
stagingis refused, then merge the release PR and check that the unfreeze and the sync both succeed.Additional Media:
Checklist:
🤖 Generated with Claude Code