Skip to content

Updates wording for Restricted Contexts requirements #9347

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

Open
wants to merge 3 commits into
base: master
Choose a base branch
from
Open
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion jekyll/_cci2/contexts.adoc
Original file line number Diff line number Diff line change
Expand Up @@ -97,7 +97,7 @@ You can combine several contexts for a single job by adding them to the context
== Restrict a context


NOTE: Bitbucket repositories do *not* provide an API that allows CircleCI contexts to be restricted, only GitHub OAuth app accounts support security group restrictions. To find out which GitHub account type you have, refer to the xref:github-integration#[GitHub OAuth integration] page.
NOTE: Bitbucket repositories do *not* provide an API that allows CircleCI contexts to be restricted. Only GitHub OAuth app accounts support security group restrictions, including GitHub App pipelines on GitHub OAuth connected organizations. To find out which GitHub account type you have, refer to the xref:github-integration#using-github-app-functionality[GitHub OAuth integration] page. Restricting contexts for custom webhook triggers is not currently supported.

CircleCI enables you to restrict contexts at run time in the following ways:

Expand Down