GitHub Community
Environments not available on my organization #26262
-
|
Hi, I am very excited about GitHub Actions: Environments, environment protection rules and environment secrets (beta) - GitHub Changelog
It is not available into my organisation repositories only in my private repositories. Would it possible to enable it on my organization ? If yes, how ? Thanks, |
Beta Was this translation helpful? Give feedback.
Replies: 31 comments 3 replies
-
|
At this time the private repository use is only available on GitHub Enterprise Cloud so you would have to upgrade your organisation to that plan. We have detailed feature comparisons at the bottom of our pricing page. |
Beta Was this translation helpful? Give feedback.
-
|
Thanks for your answer. |
Beta Was this translation helpful? Give feedback.
-
|
We do refresh our offerings from time to time, but right now I don’t know. |
Beta Was this translation helpful? Give feedback.
-
|
I’d also be interested in using the environments feature in our Team plan. It seems like a pretty steep jump from $4/user/month to $21/user/month just to be able to manage deployments to a staging and production environment. I could totally see the environment protection rules being part of the enterprise plan but just having environments seems like a feature most small teams would want to use |
Beta Was this translation helpful? Give feedback.
-
|
Same here. We can’t afford at the moment to jump to $21/user/month. It works like a Spring Cloud config server It does not provide the features of env protections rules but, it provides at least that possibility to go over 10 inputs, trigger generic actions/workflow based on an environment variables, etc. |
Beta Was this translation helpful? Give feedback.
-
|
Same here. |
Beta Was this translation helpful? Give feedback.
-
|
Hi GitHub support, Just wanting to put some pressure on you guys, nothing but love. I really really want this feature in the Teams plan as our company is a small startup that cannot yet afford the Enterprise plan. All the best |
Beta Was this translation helpful? Give feedback.
-
|
@canuckjacq any update if this might come to the teams plan anytime soon? |
Beta Was this translation helpful? Give feedback.
-
|
Work in a Brazilian org and there’s no way we can afford the 21usd per user in the Enterprise plan. This missing feature would make a world of a difference to us. |
Beta Was this translation helpful? Give feedback.
-
|
What a bummer. We will be trying now what @Steph0 suggested and see how it works… but this definitely should be considered for free version (or at least Dev one). |
Beta Was this translation helpful? Give feedback.
-
|
I come here to put a +1. That feature is great and it would help us to properly require approvals to deploy. Sadly we’re a small bootstrapped team so the jump in pricing is too big for us. |
Beta Was this translation helpful? Give feedback.
-
|
Locking security features behind a paywall is an antipattern, you should really reconsider-- especially considering actions is becoming a larger and larger part of the ci cd ecosystem. Branch protection and environments need to be unlocked. |
Beta Was this translation helpful? Give feedback.
-
|
Are there plans to add support for this on the Team plan? The $21/user/month of the enterprise is a no-go for us |
Beta Was this translation helpful? Give feedback.
-
|
This definitely should be added to the Teams plan, not strictly limited to the Enterprise. It’s a shame to limit this feature which everyone should be using to just Enterprise. |
Beta Was this translation helpful? Give feedback.
-
|
I think it was announced like beta so it is part of enterprise plan for limiting users. |
Beta Was this translation helpful? Give feedback.
-
|
+1 on adding it to the Team plan. |
Beta Was this translation helpful? Give feedback.
-
|
+1 need this feature. |
Beta Was this translation helpful? Give feedback.
-
|
+1 regarding adding the environments management for at least Team plan. It is pitty we started with GitHub and now we have to consider alternatives because of this. It would help to know the roadmap if it is even on the table or the only solution is Enterprice plan. |
Beta Was this translation helpful? Give feedback.
-
|
need this. |
Beta Was this translation helpful? Give feedback.
-
|
It looks like this was recently added to the Team plan 😃 |
Beta Was this translation helpful? Give feedback.
-
|
@Kowaman you are absolutely right 🎉 , we can see that on the updated env page, seems thought that some features like reviewers / manual approval are still restricted to enterprise 😢 |
Beta Was this translation helpful? Give feedback.
-
|
That sucks |
Beta Was this translation helpful? Give feedback.
-
|
In environment approval for enterprise account, reviewers option not showing. |
Beta Was this translation helpful? Give feedback.
-
|
need approval on team plan . |
Beta Was this translation helpful? Give feedback.
-
|
In the absence of this how are people managing their production releases? We need a pipeline that deploys to UAT and then Production after a review and approval. What are people doing to prevent builds going straight to production following a UAT release? The only way would be to replicate the CI/CD for each environment and kick them off manually? |
Beta Was this translation helpful? Give feedback.
-
|
We have a separate repository with a different set of user accesses for what you call a production release. The necessary secrets are also only available there. You can't mimic Environments with branch protection rules, for example, because all people can see all branches in a given repo. Thus, anyone could take the prod release workflow and run in another branch. |
Beta Was this translation helpful? Give feedback.
-
|
Github, could you clarify this feature in the docs [1]? It reads:
But I don't see environments anywhere neither in org settings, nor in public repo settings. We seem to be on a legacy plan and most our repos are public and open source. So according to the above description, environments should be available in those. |
Beta Was this translation helpful? Give feedback.
-
|
Github team, please provide some clarifications. This was a requirement for us to move from circleCI to Github actions and according to the docs it should work as we are on the GH teams plan. So I started the migration and almost finished until I find out it doesn't work although it says so in the docs: Please advise as this is a really important feature |
Beta Was this translation helpful? Give feedback.
-
|
Please give an update on this as the docs are misleading. I was configuring this thinking i found a solution for manual approvals. only to find out the deployment rules options are not present in Team. |
Beta Was this translation helpful? Give feedback.
-
|
Please add this feature to github team plan, our org want this so bad ! |
Beta Was this translation helpful? Give feedback.
-
|
Hi, I am very excited about GitHub Actions: Environments, environment protection rules and environment secrets (beta) - GitHub Changelog In this open beta there is no need to sign up, all existing GitHub organizations and accounts can use the new capabilities in their public repositories and GitHub Enterprise Cloud organizations can use them in all repositories. It is not available into my organisation repositories only in my private repositories. Would it possible to enable it on my organization ? If yes, how ? Thanks, |
Beta Was this translation helpful? Give feedback.
-
|
Friends, may I suggest you have a look at PORT => https://docs.getport.io/ This is not for Kubernetes only, PORT works for any kind of projects and setups |
Beta Was this translation helpful? Give feedback.
-
|
can you at least show that this feature is not available for unpaid orgs? |
Beta Was this translation helpful? Give feedback.
and others
At this time the private repository use is only available on GitHub Enterprise Cloud so you would have to upgrade your organisation to that plan.
We have detailed feature comparisons at the bottom of our pricing page.