Conversation
- Changed 'Organization Home' to 'Home' - Changed 'Chunk Tasks' to 'Tasks' - Changed 'Self-Hosted Runners' to 'Runners' (menu references) - Changed 'Organization Settings' to 'Org' Updated all instances across documentation files including: - User guides and tutorials - Configuration and setup instructions - Security and permissions documentation - Integration guides - API and CLI documentation - Orb documentation Resolves DOC-26 Co-authored-by: Rosie Yohannan <rosieyohannan@users.noreply.github.com>
|
Cursor Agent can help with this pull request. Just |
rosieyohannan
left a comment
There was a problem hiding this comment.
@cursoragent changes required
| === Amazon Bedrock authentication error or 401 | ||
|
|
||
| Your AWS bearer token is invalid or has expired. Regenerate the token in AWS IAM and update it in the `circleci-agents` context in **Organization Settings** > **Contexts**. | ||
| Your AWS bearer token is invalid or has expired. Regenerate the token in AWS IAM and update it in the `circleci-agents` context in **Org** > **Contexts**. |
There was a problem hiding this comment.
| Your AWS bearer token is invalid or has expired. Regenerate the token in AWS IAM and update it in the `circleci-agents` context in **Org** > **Contexts**. | |
| Your AWS bearer token is invalid or has expired. Regenerate the token in AWS IAM and update it in the `circleci-agents` context in menu:Org[Contexts]. |
| If organization verification is not possible, you can bypass this requirement by adding an environment variable to your `circleci-agents` context as follows: | ||
|
|
||
| . In the CircleCI web app, go to **Organization Settings** > **Contexts**. | ||
| . In the CircleCI web app, go to **Org** > **Contexts**. |
There was a problem hiding this comment.
| . In the CircleCI web app, go to **Org** > **Contexts**. | |
| . In the CircleCI web app, go to menu:Org[Contexts]. |
| . Select **Delete** to delete the environment variable. You will be prompted to confirm the deletion. | ||
|
|
||
| NOTE: **CircleCI (Powered by Anthropic) users.** If you are using the CircleCI-managed provider, there is no API key stored in your context. To remove Chunk access, disable the **Allow Chunk tasks** toggle in **Organization Settings** > **Advanced**. | ||
| NOTE: **CircleCI (Powered by Anthropic) users.** If you are using the CircleCI-managed provider, there is no API key stored in your context. To remove Chunk access, disable the **Allow Chunk tasks** toggle in **Org** > **Advanced**. |
There was a problem hiding this comment.
| NOTE: **CircleCI (Powered by Anthropic) users.** If you are using the CircleCI-managed provider, there is no API key stored in your context. To remove Chunk access, disable the **Allow Chunk tasks** toggle in **Org** > **Advanced**. | |
| NOTE: **CircleCI (Powered by Anthropic) users.** If you are using the CircleCI-managed provider, there is no API key stored in your context. To remove Chunk access, disable the **Allow Chunk tasks** toggle in menu:Org[Advanced]. |
| * The CircleCI GitHub App installed in your organization. Check **Organization Settings** > **VCS Connections**. Chunk needs the GitHub App to recommend fixes and open pull requests. | ||
| * The **Allow Chunk tasks** option enabled for your organization. Navigate to **Organization Settings** > **Advanced** and toggle on **Allow Chunk tasks**. | ||
| * The CircleCI GitHub App installed in your organization. Check **Org** > **VCS Connections**. Chunk needs the GitHub App to recommend fixes and open pull requests. | ||
| * The **Allow Chunk tasks** option enabled for your organization. Navigate to **Org** > **Advanced** and toggle on **Allow Chunk tasks**. |
There was a problem hiding this comment.
| * The **Allow Chunk tasks** option enabled for your organization. Navigate to **Org** > **Advanced** and toggle on **Allow Chunk tasks**. | |
| * The **Allow Chunk tasks** option enabled for your organization. Navigate to menu:Org[Advanced] and toggle on **Allow Chunk tasks**. |
| OpenAI organization verification required. Please verify your organization at https://platform.openai.com/settings/organization/generaland see our community forum for more debugging help. | ||
|
|
||
| To fix this issues, head to link:https://platform.openai.com/settings/organization/general[OpenAI Platform, window=_blank], navigate to menu:General[Organization Settings] and select btn:[Verify Organization]. Then follow the steps to get your organization verified. | ||
| To fix this issues, head to link:https://platform.openai.com/settings/organization/general[OpenAI Platform, window=_blank], navigate to menu:General[Org Settings] and select btn:[Verify Organization]. Then follow the steps to get your organization verified. |
There was a problem hiding this comment.
| To fix this issues, head to link:https://platform.openai.com/settings/organization/general[OpenAI Platform, window=_blank], navigate to menu:General[Org Settings] and select btn:[Verify Organization]. Then follow the steps to get your organization verified. | |
| To fix this issues, head to link:https://platform.openai.com/settings/organization/general[OpenAI Platform, window=_blank], navigate to menu:General[Organization Settings] and select btn:[Verify Organization]. Then follow the steps to get your organization verified. |
There was a problem hiding this comment.
This part is talking about openai not circleci
| [%hardbreaks] | ||
| *Invite teammates* | ||
| Invite teammates to collaborate on your projects. Navigate to *Organization Settings > People* to generate invites and get further instructions. Collaborators can view and follow your projects. Teammates can make a free CircleCI account at any time to view your pipelines, even if they are not committing any code. | ||
| Invite teammates to collaborate on your projects. Navigate to *Org > People* to generate invites and get further instructions. Collaborators can view and follow your projects. Teammates can make a free CircleCI account at any time to view your pipelines, even if they are not committing any code. |
There was a problem hiding this comment.
| Invite teammates to collaborate on your projects. Navigate to *Org > People* to generate invites and get further instructions. Collaborators can view and follow your projects. Teammates can make a free CircleCI account at any time to view your pipelines, even if they are not committing any code. | |
| Invite teammates to collaborate on your projects. Navigate to menu:Org[People] to generate invites and get further instructions. Collaborators can view and follow your projects. Teammates can make a free CircleCI account at any time to view your pipelines, even if they are not committing any code. |
| If you need immediate relief to restore workflows during an active brownout, you can temporarily disable brownouts. | ||
|
|
||
| Navigate to *Organization Settings > Advanced > Enable resource class brownouts* and toggle the setting off. | ||
| Navigate to *Org > Advanced > Enable resource class brownouts* and toggle the setting off. |
There was a problem hiding this comment.
| Navigate to *Org > Advanced > Enable resource class brownouts* and toggle the setting off. | |
| Navigate to menu:Org[Advanced > Enable resource class brownouts] and toggle the setting off. |
| == Organization settings | ||
|
|
||
| The following organization settings are available by selection "Organization Settings" in the sidebar: | ||
| The following organization settings are available by selecting "Org" in the sidebar: |
There was a problem hiding this comment.
| The following organization settings are available by selecting "Org" in the sidebar: | |
| The following organization settings are available by selecting *Org* from the sidebar: |
archive/gitlab-integration.adoc
Outdated
| For GitLab integrations, organizations and users are managed independently from your VCS. Organizations and users are considered CircleCI organizations and users, with their own roles and permissions that do not rely on those defined in your VCS. | ||
|
|
||
| To manage settings at the organization level, select btn:[Organization Settings] in the CircleCI web app sidebar. | ||
| To manage settings at the organization level, select btn:[Org] in the CircleCI web app sidebar. |
There was a problem hiding this comment.
| To manage settings at the organization level, select btn:[Org] in the CircleCI web app sidebar. | |
| To manage settings at the organization level, select *Org* in the CircleCI web app sidebar. |
| For Bitbucket Data Center integrations, organizations and users are managed independently from your VCS. Organizations and users are considered CircleCI organizations and users, with their own roles and permissions that do not rely on those defined in your VCS. | ||
|
|
||
| To manage settings at the organization level, select btn:[Organization Settings] in the CircleCI web app sidebar. | ||
| To manage settings at the organization level, select btn:[Org] in the CircleCI web app sidebar. |
There was a problem hiding this comment.
| To manage settings at the organization level, select btn:[Org] in the CircleCI web app sidebar. | |
| To manage settings at the organization level, select *Org* in the CircleCI web app sidebar. |
|
I've addressed all the feedback from the PR review. Here's what was fixed: Changes Made:
All changes have been committed and pushed to the branch. The PR should now conform to the CircleCI documentation style guidelines. |
- Reverted OpenAI 'Organization Settings' change (was incorrectly changed to 'Org Settings') - Updated to use menu: syntax for consistency (menu:Org[...]) - Changed 'click' to 'select' and 'go to' to more consistent phrasing - Changed 'on the left navigation' to 'from the sidebar' - Changed https:// to link: syntax where appropriate - Removed btn:[] formatting where simple bold (*) is more appropriate Co-authored-by: Rosie Yohannan <rosieyohannan@users.noreply.github.com>
The Integrations page in the CircleCI app has been moved to VCS Connections. Updated all references throughout the documentation to reflect this change. Changes: - menu:Org[Integrations] → menu:Org[VCS Connections] - 'Integrations page under Org' → 'VCS Connections page under Org' - 'Navigate to **Integrations** within **Org**' → 'Navigate to **VCS Connections** within **Org**' Co-authored-by: Rosie Yohannan <rosieyohannan@users.noreply.github.com>
Archive files should not be modified as they contain historical documentation. Co-authored-by: Rosie Yohannan <rosieyohannan@users.noreply.github.com>


[!NOTE]
Description
Updated references to CircleCI app sidebar menu items to reflect recent UI changes.
Reasons
The CircleCI app sidebar menu items have been renamed. This PR updates the documentation to ensure consistency with the current application interface, resolving DOC-26.
Specifically, the following changes were made:
Organization Home→HomeChunk Tasks→TasksSelf-Hosted Runner→RunnersOrganization Settings→OrgContent checks
Please follow our style when contributing to CircleCI docs. View our style guide or check out our CONTRIBUTING.md for more information.
Preview your changes:
ci/circleci: lintjob at the bottom of your PR. You will be redirected to thevale/lintjob output in CircleCI.ci/circleci: buildjob at the bottom of your PR and you will be redirected to CircleCI. Select the Artifacts tab and selectindex.htmlto open a preview version of the docs site built for your latest commit.Take a moment to check through the following items when submitting your PR (this is just a guide so will not be relevant for all PRs):
Content structure:
Formatting:
Linear Issue: DOC-26