Skip to content
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

Repo sync #35526

Merged
merged 8 commits into from
Dec 2, 2024
Prev Previous commit
Next Next commit
Clarifying about actions availability in EMU (#53323)
Co-authored-by: Isaac Brown <101839405+isaacmbrown@users.noreply.github.com>
  • Loading branch information
andrekolodochka and isaacmbrown authored Dec 2, 2024
commit 140fd66ed2a37a1d96e50e83217fcc4728234766
Original file line number Diff line number Diff line change
Expand Up @@ -25,7 +25,7 @@ With {% data variables.product.prodname_emus %}, you can control the user accoun
## {% data variables.product.prodname_actions %}

* {% data variables.enterprise.prodname_managed_users_caps %} cannot create workflow templates for {% data variables.product.prodname_actions %}.
* Entitlement minutes for {% data variables.product.company_short %}-hosted runners are not available for {% data variables.enterprise.prodname_managed_users %}.
* While {% data variables.product.company_short %}-hosted runners can be used in repositories owned by organizations, they are not available for repositories owned by {% data variables.enterprise.prodname_managed_users %}.
* {% data variables.product.prodname_emus %} can trigger workflows in organizations where they are not members by forking the organization repository, then creating a pull request targeting the organization repository.

## {% data variables.product.prodname_github_apps %}
Expand Down
Loading