-
Notifications
You must be signed in to change notification settings - Fork 15
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 repo to django org #56
Comments
Hey @deepakdinesh1123 — thanks for this. I have some preparatory work for releases next week, and then I will swing to this and look at what needs to happen. |
Hi Carlton -- I had another look at the settings for this repo and can't see anywhere where I can grant extra privilages. Let me know if you need me to do anything to transfer the repo. |
Thanks @smithdc1. It's been a busy week ... 😅. My plan is to pick this up next week. |
Hey @smithdc1 — Right, so you have to go to the repo settings and then down the bottom there's a "Danger Zone" where the option to transfer is... If you click that, hopefully I'll get a notification, and can pick up from there. 🤞 |
Maybe I could move to crispy-forms org and you could pick up from there? |
@smithdc1 I've adjusted Django Org member permissions for the moment, can you try again? Thanks! |
@carltongibson -- Done! 🎉 |
Well done. Thanks! |
I have added the workflow to run the benchmarks when a pull request is labeled in the
django\django
repo here, Mariusz Felisiak mentioned in a comment that moving this repo to the django organization would be better as the workflow wouldn't depend on any user repositories.Should the repo be moved? Are there any changes that I need to make before moving?
The text was updated successfully, but these errors were encountered: