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

migrated namespace from TimothyStiles/poly to bebop/poly #416

Merged
merged 1 commit into from
Dec 11, 2023

Conversation

TimothyStiles
Copy link
Collaborator

@TimothyStiles TimothyStiles commented Dec 11, 2023

Changes in this PR

It's finally time to move poly from my personal account to an org account. This will change the namespace from TimothyStiles/Poly to bebop/poly

Why are you making these changes?

Two main reasons:

  1. We want to onboard more core and associate devs with more fine grained controls which only a GitHub org has.
  2. Funding organizations and fiscal sponsors have problems funding us if it's under my personal account.

Also the bebop org name is cool and we should use it.

Are any changes breaking? (IMPORTANT)

Will merging this PR change poly's API in a non-backwards-compatible manner?

It definitely break some namespace and reference links which this PR is attempting to fix.

Pre-merge checklist

All of these must be satisfied before this PR is considered
ready for merging. Mergeable PRs will be prioritized for review.

  • All code is properly formatted and linted.
  • The PR template is filled out.

@TimothyStiles TimothyStiles merged commit 4460c3b into main Dec 11, 2023
4 checks passed
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

Successfully merging this pull request may close these issues.

None yet

1 participant