-
Notifications
You must be signed in to change notification settings - Fork 663
Add repo migration notice workflows #3127
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
jdetter
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Me and Zeke sync'd about this over discord - these workflows will never run on PRs within the SpacetimeDB repo but we're trying to keep the subdirectories within SpacetimeDB in-sync with the deprecated repos so that rolling releases isn't as complicated.
|
Now that this PR is merged, I will start deploying to the repos, and update the following checklist:
|
|
I'm done deploying these changes to all the repos above. I'm going to try opening a random PR in each one, and confirm that it worked with the following checkboxes:
|
# Description of Changes Added a repo migration notice workflow to each repository that we've merged into SpacetimeDB. These need to be mirrored back to the actual repos with a process like: ```bash git subtree split --prefix=sdks/typescript -b release/typescript git push -f git@github.com:clockworklabs/spacetimedb-typescript-sdk.git release/typescript:main git branch -D release/typescript ``` Once they're migrated there, the bot will automatically comment on any PR or issue opened in those repos. # API and ABI breaking changes None. CI-only changes. # Expected complexity level and risk 2 # Testing - [x] In a demo repo, it properly commented and closed a PR: clockworklabs/github-tooling-test#42 - [x] In a demo repo, it properly commented and closed an issue: clockworklabs/github-tooling-test#43 --------- Co-authored-by: Zeke Foppa <bfops@users.noreply.github.com>
# Description of Changes Added a repo migration notice workflow to each repository that we've merged into SpacetimeDB. These need to be mirrored back to the actual repos with a process like: ```bash git subtree split --prefix=sdks/typescript -b release/typescript git push -f git@github.com:clockworklabs/spacetimedb-typescript-sdk.git release/typescript:main git branch -D release/typescript ``` Once they're migrated there, the bot will automatically comment on any PR or issue opened in those repos. # API and ABI breaking changes None. CI-only changes. # Expected complexity level and risk 2 # Testing - [x] In a demo repo, it properly commented and closed a PR: clockworklabs/github-tooling-test#42 - [x] In a demo repo, it properly commented and closed an issue: clockworklabs/github-tooling-test#43 --------- Co-authored-by: Zeke Foppa <bfops@users.noreply.github.com>
# Description of Changes Added a repo migration notice workflow to each repository that we've merged into SpacetimeDB. These need to be mirrored back to the actual repos with a process like: ```bash git subtree split --prefix=sdks/typescript -b release/typescript git push -f git@github.com:clockworklabs/spacetimedb-typescript-sdk.git release/typescript:main git branch -D release/typescript ``` Once they're migrated there, the bot will automatically comment on any PR or issue opened in those repos. # API and ABI breaking changes None. CI-only changes. # Expected complexity level and risk 2 # Testing - [x] In a demo repo, it properly commented and closed a PR: clockworklabs/github-tooling-test#42 - [x] In a demo repo, it properly commented and closed an issue: clockworklabs/github-tooling-test#43 --------- Co-authored-by: Zeke Foppa <bfops@users.noreply.github.com>
Description of Changes
Added a repo migration notice workflow to each repository that we've merged into SpacetimeDB.
These need to be mirrored back to the actual repos with a process like:
Once they're migrated there, the bot will automatically comment on any PR or issue opened in those repos.
API and ABI breaking changes
None. CI-only changes.
Expected complexity level and risk
2
Testing