-
Notifications
You must be signed in to change notification settings - Fork 73
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
Moving to organization based repo #71
Comments
That's really sweet. :) I think there's a way to transfer a repo to a new owner, including all issues and stars etc. I would suggest you scrap the cloned repo and then transfer this one over (I think there's a button in your repo settings). |
@skosch Its not a bother - I will take a look as soon as I'm out of the hospital (most probably beginning of the next week). Sorry for the delay |
Oh no! In that case, take your time 😧 hope you're doing okay! |
It was a pretty light surgery - I'm doing just fine :) So as you can see I transferred the repo to our organization (Thanks for the suggestion - I wasn't aware that we can do that). I've also took a look at the inline images branch and updated the ticket for my comments. |
Excellent, thank you, and I hope you'll be back on your feet soon! I think we can close this thread then :) |
@skosch @Ch4s3
I figured that keeping the project under my account could be misleading as to the origins of efforts from now on. Because of this, I've just created a new organization in GitHub for the project and invited you both: mailman-elixir.
The repo has been cloned over there and lives at: https://github.com/mailman-elixir/mailman
Could you please make sure you have the needed access? It's becoming our baby from now on :)
The text was updated successfully, but these errors were encountered: