-
Notifications
You must be signed in to change notification settings - Fork 10
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
add ember versions 3.19-3.25 #40
base: master
Are you sure you want to change the base?
Conversation
@wifelette @chancancode Maybe you could give @yads access so he can deploy this. |
I'll investigate on Monday! 👍 |
I'll try to set it up so that merging will automatically deploy on CI so we don't have to worry about keys anymore, just commit bit on GitHub. |
Can we transfer this repo into ember-cli org so I can set it up? |
@chancancode deploy is manual and one deploy per ember version |
Yep I understand. In general we are trying to avoid giving out new keys to things and instead automate them where possible and let GH be the only place we need to manage access control. We did that last year with the docs S3 deploy. I would like to investigate the possibility of doing the same here as it’s generally how we would like to move forward with these things. |
@chancancode Only a collaborator on this repo and can't transfer it. |
I'm 👍🏼 on moving to cli org and lowering barrier and increasing security for deployment. |
No description provided.