Skip to content

Conversation

@yads
Copy link

@yads yads commented Feb 23, 2021

No description provided.

@Gaurav0
Copy link
Collaborator

Gaurav0 commented Feb 28, 2021

@wifelette @chancancode Maybe you could give @yads access so he can deploy this.

@chancancode
Copy link

I'll investigate on Monday! 👍

@chancancode
Copy link

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.

@chancancode
Copy link

Can we transfer this repo into ember-cli org so I can set it up?

@Gaurav0
Copy link
Collaborator

Gaurav0 commented Mar 1, 2021

@chancancode deploy is manual and one deploy per ember version

@chancancode
Copy link

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.

@Gaurav0
Copy link
Collaborator

Gaurav0 commented Mar 1, 2021

@chancancode Only a collaborator on this repo and can't transfer it.

@knownasilya
Copy link

I'm 👍🏼 on moving to cli org and lowering barrier and increasing security for deployment.

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.

4 participants