Skip to content

#QA77 - semrush fixes#11

Open
SarpBakis23 wants to merge 1 commit into
developfrom
feature/qa-77
Open

#QA77 - semrush fixes#11
SarpBakis23 wants to merge 1 commit into
developfrom
feature/qa-77

Conversation

@SarpBakis23

@SarpBakis23 SarpBakis23 commented Jul 17, 2026

Copy link
Copy Markdown
Contributor

Summary by CodeRabbit

  • Documentation
    • Simplified descriptions across account, build, workflow, publishing, environment, and self-hosted Appcircle documentation pages.
    • Updated SSO provider links to point to the current authentication guidance.
    • Improved documentation discoverability by using clearer, more focused page summaries.
  • Chores
    • Prevented search engines from crawling tag pages while retaining sitemap access.

@SarpBakis23
SarpBakis23 requested a review from ozcanovunc July 17, 2026 09:21
@SarpBakis23 SarpBakis23 self-assigned this Jul 17, 2026
@coderabbitai

coderabbitai Bot commented Jul 17, 2026

Copy link
Copy Markdown

Review Change Stack

📝 Walkthrough

Walkthrough

Changes

The pull request shortens or reframes front-matter descriptions across documentation pages, updates SSO provider links to a shared authentication page, and adds a /tags/ crawler exclusion while retaining the sitemap.

Documentation updates

Layer / File(s) Summary
Page description updates
docs/account/..., docs/appcircle-ai/..., docs/build/..., docs/environment-variables/..., docs/publish-..., docs/self-hosted-appcircle/..., docs/workflows/...
Documentation descriptions are replaced with shorter, more focused wording across organization, build, publishing, environment, self-hosted, runner, and workflow pages.
SSO documentation links
docs/self-hosted-appcircle/.../integrations-and-access/integration.md
SSO provider links now point to the shared SSO authentication provider-configuration section.

Crawler rules

Layer / File(s) Summary
Tags crawl exclusion
static/robots.txt
All user agents are instructed not to crawl /tags/; the sitemap directive remains unchanged.

Poem

I’m a rabbit with docs in my den,
Shorter descriptions hop into view again.
SSO links leap to their proper trail,
Tags hide quietly behind a crawl-proof veil.
The sitemap still shines—what a tale!

🚥 Pre-merge checks | ✅ 1 | ❌ 1

❌ Failed checks (1 inconclusive)

Check name Status Explanation Resolution
Title check ❓ Inconclusive The title is related to the SEO/metadata changes, but it is too vague to describe the actual doc updates. Rename it to mention the main change, such as updating documentation meta descriptions and robots.txt for SEO.
✅ Passed checks (1 passed)
Check name Status Explanation
Description Check ✅ Passed Check skipped - CodeRabbit’s high-level summary is enabled.
✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch feature/qa-77
✨ Simplify code
  • Create PR with simplified code
  • Commit simplified code in branch feature/qa-77

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands.

@cloudflare-workers-and-pages

Copy link
Copy Markdown

Deploying with  Cloudflare Workers  Cloudflare Workers

The latest updates on your project. Learn more about integrating Git with Workers.

Status Name Latest Commit Preview URL Updated (UTC)
✅ Deployment successful!
View logs
appcircle-docs 0c3c10b Commit Preview URL

Branch Preview URL
Jul 17 2026, 09:22 AM

@cloudflare-workers-and-pages

Copy link
Copy Markdown

Deploying with  Cloudflare Workers  Cloudflare Workers

The latest updates on your project. Learn more about integrating Git with Workers.

Status Name Latest Commit Preview URL Updated (UTC)
✅ Deployment successful!
View logs
appcircle-docs 0c3c10b Commit Preview URL

Branch Preview URL
Jul 17 2026, 09:22 AM

@coderabbitai coderabbitai Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 3

🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

Inline comments:
In `@docs/account/my-organization/profile-and-team/team-activity-log.md`:
- Line 3: Update the page description metadata in the front matter to use the
grammatically correct phrase “the Organization Activity Log,” preserving the
rest of the description unchanged.

In
`@docs/self-hosted-appcircle/install-server/helm-chart/configuration/domain-verification.md`:
- Line 4: Normalize the metadata descriptions at
docs/self-hosted-appcircle/install-server/helm-chart/configuration/domain-verification.md:4-4
to “Learn how to configure domain verification for the Appcircle Helm chart.”,
docs/self-hosted-appcircle/install-server/helm-chart/configuration/production-readiness/s3-compatible-storage-configuration.md:3-3
to use “for the Appcircle server,” and
docs/self-hosted-appcircle/install-server/linux-package/configure-server/domain-verification.md:4-4
to “Learn how to configure domain verification for the Appcircle Linux package.”

In `@docs/workflows/common-workflow-steps/aws-device-farm-and-deploy.md`:
- Line 3: Update the descriptions at
docs/workflows/common-workflow-steps/aws-device-farm-and-deploy.md:3 and
docs/workflows/common-workflow-steps/git-clone.md:3 to include “the” before the
named workflow step, using the exact corrected wording specified in the review.
🪄 Autofix (Beta)

Fix all unresolved CodeRabbit comments on this PR:

  • Push a commit to this branch (recommended)
  • Create a new PR with the fixes

ℹ️ Review info
⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: 56fdef35-ac05-4904-a2cd-dad11b23335a

📥 Commits

Reviewing files that changed from the base of the PR and between 55d0e42 and 0c3c10b.

📒 Files selected for processing (33)
  • docs/account/my-organization/index.md
  • docs/account/my-organization/notifications/teams-notifications.md
  • docs/account/my-organization/notifications/webhooks.md
  • docs/account/my-organization/profile-and-team/team-activity-log.md
  • docs/account/my-organization/profile-and-team/team-management.md
  • docs/appcircle-ai/ai-insights/build-insights.md
  • docs/build/build-process-management/index.md
  • docs/build/platform-build-guides/building-ios-applications.md
  • docs/enterprise-app-store/in-app-updates/index.md
  • docs/environment-variables/index.md
  • docs/environment-variables/platform-specific-usage/index.md
  • docs/publish-integrations/ios-publish-integrations/index.md
  • docs/publish-module/publish-resign-report/index.md
  • docs/self-hosted-appcircle/install-server/helm-chart/configuration/domain-verification.md
  • docs/self-hosted-appcircle/install-server/helm-chart/configuration/production-readiness/s3-compatible-storage-configuration.md
  • docs/self-hosted-appcircle/install-server/helm-chart/installation/installation-modes.md
  • docs/self-hosted-appcircle/install-server/linux-package/configure-server/advanced-configuration/index.md
  • docs/self-hosted-appcircle/install-server/linux-package/configure-server/domain-verification.md
  • docs/self-hosted-appcircle/install-server/linux-package/configure-server/index.md
  • docs/self-hosted-appcircle/install-server/linux-package/configure-server/integrations-and-access/index.md
  • docs/self-hosted-appcircle/install-server/linux-package/configure-server/integrations-and-access/integration.md
  • docs/self-hosted-appcircle/self-hosted-runner/cloud-providers/index.md
  • docs/self-hosted-appcircle/self-hosted-runner/configure-runner/index.md
  • docs/workflows/android-specific-workflow-steps/appdome-build-to-secure-for-android.md
  • docs/workflows/android-specific-workflow-steps/browserstack-app-automate-espresso.md
  • docs/workflows/common-workflow-steps/artifactory-repository-management/jfrof-repository-management.md
  • docs/workflows/common-workflow-steps/artifactory-repository-management/nexus-repository-management.md
  • docs/workflows/common-workflow-steps/aws-device-farm-and-deploy.md
  • docs/workflows/common-workflow-steps/custom-script-from-git.md
  • docs/workflows/common-workflow-steps/data-theorem-mobile-secure.md
  • docs/workflows/common-workflow-steps/git-clone.md
  • docs/workflows/common-workflow-steps/saucectl-run.md
  • static/robots.txt

---
title: Organization Activity
description: Appcircle will notify external services via webhooks when a certain event occurs. When the events you specified happen, we'll send a POST request in JSON format to the URLs you provide. (Team Activity Log)
description: Learn more about Organization Activity Log in Appcircle.

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

📐 Maintainability & Code Quality | 🟡 Minor | ⚡ Quick win

Fix the article in the page description.

Use “the Organization Activity Log” for grammatically correct metadata.

Proposed fix
-description: Learn more about Organization Activity Log in Appcircle.
+description: Learn more about the Organization Activity Log in Appcircle.
📝 Committable suggestion

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

Suggested change
description: Learn more about Organization Activity Log in Appcircle.
description: Learn more about the Organization Activity Log in Appcircle.
🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

In `@docs/account/my-organization/profile-and-team/team-activity-log.md` at line
3, Update the page description metadata in the front matter to use the
grammatically correct phrase “the Organization Activity Log,” preserving the
rest of the description unchanged.

title: Domain Verification for Helm Chart Configuration
sidebar_label: Domain Verification
description: Configure the Appcircle server to bypass domain verification when adding domains to an organization or verify them using DNS records on Kubernetes/OpenShift architecture.
description: Learn to configure Domain Verification for Helm Chart.

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

📐 Maintainability & Code Quality | 🟡 Minor | ⚡ Quick win

Normalize the wording of these descriptions. The updated metadata has minor article and phrasing issues that reduce polish in search snippets.

  • docs/self-hosted-appcircle/install-server/helm-chart/configuration/domain-verification.md#L4-L4: use “Learn how to configure domain verification for the Appcircle Helm chart.”
  • docs/self-hosted-appcircle/install-server/helm-chart/configuration/production-readiness/s3-compatible-storage-configuration.md#L3-L3: change “for Appcircle server” to “for the Appcircle server.”
  • docs/self-hosted-appcircle/install-server/linux-package/configure-server/domain-verification.md#L4-L4: use “Learn how to configure domain verification for the Appcircle Linux package.”
📍 Affects 3 files
  • docs/self-hosted-appcircle/install-server/helm-chart/configuration/domain-verification.md#L4-L4 (this comment)
  • docs/self-hosted-appcircle/install-server/helm-chart/configuration/production-readiness/s3-compatible-storage-configuration.md#L3-L3
  • docs/self-hosted-appcircle/install-server/linux-package/configure-server/domain-verification.md#L4-L4
🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

In
`@docs/self-hosted-appcircle/install-server/helm-chart/configuration/domain-verification.md`
at line 4, Normalize the metadata descriptions at
docs/self-hosted-appcircle/install-server/helm-chart/configuration/domain-verification.md:4-4
to “Learn how to configure domain verification for the Appcircle Helm chart.”,
docs/self-hosted-appcircle/install-server/helm-chart/configuration/production-readiness/s3-compatible-storage-configuration.md:3-3
to use “for the Appcircle server,” and
docs/self-hosted-appcircle/install-server/linux-package/configure-server/domain-verification.md:4-4
to “Learn how to configure domain verification for the Appcircle Linux package.”

---
title: AWS Device Farm and Deploy
description: AWS Device Farm is an application testing service that enables you to run your tests concurrently on multiple mobile devices to speed up the execution of your tests and generates videos and logs to help you quickly identify issues with your app.
description: Learn how to use AWS Device Farm and Deploy step in Appcircle.

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

📐 Maintainability & Code Quality | 🟡 Minor | ⚡ Quick win

Correct the workflow-step descriptions’ grammar.

Both descriptions omit the article before the named workflow step:

  • docs/workflows/common-workflow-steps/aws-device-farm-and-deploy.md#L3-L3: use “Learn how to use the AWS Device Farm and Deploy step in Appcircle.”
  • docs/workflows/common-workflow-steps/git-clone.md#L3-L3: use “Learn how to use the Git Clone step in Appcircle.”
📍 Affects 2 files
  • docs/workflows/common-workflow-steps/aws-device-farm-and-deploy.md#L3-L3 (this comment)
  • docs/workflows/common-workflow-steps/git-clone.md#L3-L3
🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

In `@docs/workflows/common-workflow-steps/aws-device-farm-and-deploy.md` at line
3, Update the descriptions at
docs/workflows/common-workflow-steps/aws-device-farm-and-deploy.md:3 and
docs/workflows/common-workflow-steps/git-clone.md:3 to include “the” before the
named workflow step, using the exact corrected wording specified in the review.

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.

2 participants