-
Notifications
You must be signed in to change notification settings - Fork 157
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
new development/deployment/release process #346
Conversation
@opentensor/cerebrum breaking change detected! Please prepare accordingly! |
a738099
to
e5e3048
Compare
e5e3048
to
cada696
Compare
note: should probably add a PR template for the companion PRs 🤔 |
issue_number: context.issue.number, | ||
owner: context.repo.owner, | ||
repo: context.repo.repo, | ||
body: '@opentensor/cerebrum / @opentensor/gyrus / @opentensor/cortex breaking change detected! Please prepare accordingly!' |
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.
Have we resolved permissioning issues with these alerts?
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.
I doubt it, @garrett-opentensor will need to make sure each of those groups has permissions to receive notifications in github
Fixes #344
note that this merges into
main
because that is what determines the root CI settings for the repo once we change default branch back tomain
. May need to backport as well if there are still lingering branches on the day this is merged, but the idea of this PR is that once it is merged, all new PRs targetmain
, so we shouldn't need towill want to merge on the same day @garrett-opentensor makes the proper changes to the repo/branch protection settings, which are outlined in detail in the "branches" section of
CONTRIBUTING.md