Skip to content
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

Transfer rules_dotnet to bazel-contrib #451

Closed
1 of 4 tasks
meteorcloudy opened this issue Sep 17, 2024 · 5 comments
Closed
1 of 4 tasks

Transfer rules_dotnet to bazel-contrib #451

meteorcloudy opened this issue Sep 17, 2024 · 5 comments

Comments

@meteorcloudy
Copy link

meteorcloudy commented Sep 17, 2024

Description:

This issue proposes transferring the rules_dotnet repository from the bazelbuild GitHub organization to the bazel-contrib GitHub organization, which is owned by the Community for Bazel project under the Linux Foundation.

GitHub Discussion: https://github.com/orgs/bazelbuild/discussions/2

Impacts:

  • GitHub issues & PRs will be transferred to the new repository.
  • Branch protection rules will need to be transferred to the new repository.
  • Individual maintainers will be transferred to the new repository.
  • GitHub teams will NOT be transferred to the new repository and will need to be re-created.
  • Bazel CI configurations will need to be updated to point to the new repository.

Read more on Transferring a repository from GitHub documentation.

Checklist:

@alexeagle
Copy link

Notes from SIG meeting: this transfer was unanimously approved by a thumbs-up vote.

@purkhusid
Copy link
Collaborator

Is there anything I have to do as a maintainer?

@meteorcloudy
Copy link
Author

@purkhusid Sorry for missing you in the maintainers list. Can you please officially approve this transfer? I'll then execute the transfer.

@purkhusid
Copy link
Collaborator

Yup, I approve of the transfer.

@meteorcloudy
Copy link
Author

Done

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants