Added no follow links as per SEO team suggestions#98
Conversation
Added no follow links as per SEO team suggestions
WalkthroughThis pull request converts Markdown-style links to HTML anchor tags with Changes
Estimated code review effort🎯 1 (Trivial) | ⏱️ ~3 minutes
Possibly related PRs
Suggested reviewers
Poem
Pre-merge checks and finishing touches✅ Passed checks (3 passed)
✨ Finishing touches🧪 Generate unit tests (beta)
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. Comment |
There was a problem hiding this comment.
Actionable comments posted: 1
🧹 Nitpick comments (1)
src/pages/docs/test-management/api-reference/overview.md (1)
42-42: HTML anchor conversion looks good; consider more descriptive link text.The HTML anchor with
rel="nofollow"is properly formatted. For better accessibility, consider using more descriptive link text instead of "here" (e.g., "API settings page").
📜 Review details
Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro
📒 Files selected for processing (13)
src/pages/docs/test-management/api-reference/modules.md(1 hunks)src/pages/docs/test-management/api-reference/overview.md(1 hunks)src/pages/docs/test-management/atto/sprint-planner/manage-sprints.md(1 hunks)src/pages/docs/test-management/ci-cd-integrations/azure-devops.md(1 hunks)src/pages/docs/test-management/ci-cd-integrations/circleci.md(1 hunks)src/pages/docs/test-management/ci-cd-integrations/github.md(1 hunks)src/pages/docs/test-management/ci-cd-integrations/jenkins.md(1 hunks)src/pages/docs/test-management/ci-cd-integrations/travis-ci.md(1 hunks)src/pages/docs/test-management/integrations/figma.md(1 hunks)src/pages/docs/test-management/integrations/jira-two-way-integration/install-and-connect-testsigma.md(1 hunks)src/pages/docs/test-management/introduction/getting-started.md(2 hunks)src/pages/docs/test-management/projects/project-settings.md(1 hunks)src/pages/docs/test-management/test-cases/folders.md(1 hunks)
🧰 Additional context used
🪛 markdownlint-cli2 (0.18.1)
src/pages/docs/test-management/atto/sprint-planner/manage-sprints.md
50-50: Unordered list indentation
Expected: 0; Actual: 3
(MD007, ul-indent)
50-50: Multiple spaces after blockquote symbol
(MD027, no-multiple-space-blockquote)
⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (1)
- GitHub Check: CI
🔇 Additional comments (11)
src/pages/docs/test-management/test-cases/folders.md (1)
42-42: HTML anchor conversion looks good.The Markdown link has been properly converted to an HTML anchor with
rel="nofollow". The syntax is correct and the link destination is preserved.src/pages/docs/test-management/ci-cd-integrations/circleci.md (1)
41-41: Prerequisite link removed and replaced with bold text.The CircleCI account prerequisite link has been removed and formatted as bold text instead. Since this is just stating a requirement rather than a critical navigation link, this change has minimal impact on user experience.
src/pages/docs/test-management/ci-cd-integrations/azure-devops.md (1)
38-38: Prerequisite formatting aligned with CI/CD integration pattern.Consistent with other CI/CD integration files—the Azure DevOps prerequisite link is replaced with bold text. No functional impact.
src/pages/docs/test-management/integrations/jira-two-way-integration/install-and-connect-testsigma.md (1)
41-41: External link properly converted with nofollow attribute.The Atlassian Marketplace link has been correctly converted to an HTML anchor with
rel="nofollow", which is appropriate for external links per SEO best practices. Syntax is correct.src/pages/docs/test-management/ci-cd-integrations/travis-ci.md (1)
41-41: Prerequisite formatting consistent across CI/CD integrations.The Travis CI prerequisite link is replaced with bold text, matching the pattern in other CI/CD integration files. No functional impact.
src/pages/docs/test-management/projects/project-settings.md (1)
46-46: Internal link converted to HTML anchor with nofollow.The "Manage Projects" link has been converted to an HTML anchor with
rel="nofollow". Syntax is correct and the link destination is preserved.src/pages/docs/test-management/ci-cd-integrations/jenkins.md (1)
41-41: Prerequisite formatting aligned with other CI/CD files.The Jenkins prerequisite link is replaced with bold text, consistent with the CI/CD integration pattern. No functional impact.
src/pages/docs/test-management/integrations/figma.md (1)
63-64: External Figma URL properly converted with nofollow.The Figma team URL has been correctly converted to an HTML anchor with
rel="nofollow"within the blockquote context. The syntax is correct and both the link text and destination are properly preserved.src/pages/docs/test-management/ci-cd-integrations/github.md (1)
38-38: Verify link removal vs. conversion approach.Line 38 removes the GitHub link reference but retains bold text formatting. Clarify whether this removal is intentional or if the link should have been converted to an HTML anchor with
rel="nofollow"for consistency with other files in this PR.src/pages/docs/test-management/api-reference/modules.md (1)
42-85: Comprehensive link conversion in API modules table is well-executed.All 44 links in the API Modules table have been consistently converted to HTML anchors with
rel="nofollow". The HTML syntax is correct, and the external Postman documentation URLs are properly referenced. The formatting is uniform across all modules and operations.src/pages/docs/test-management/introduction/getting-started.md (1)
31-31: HTML anchor conversions in getting-started.md are well-executed.All three links (prerequisites signup, login page, and sign-up link in steps) have been correctly converted to HTML anchors with
rel="nofollow". The formatting is consistent and the URLs are appropriate for the getting-started context. No issues identified.Also applies to: 48-48, 50-50
| > - The project is connected to a Jira project. | ||
| > - You have **Admin Access** in Jira to authorize the initial integration with Test Management by Testsigma. | ||
| > - You know how to create **WebHooks in Jir**a to enable real-time sync between Jira and Test Management by Testsigma. For more information, see [Creating WebHooks in Jira](https://developer.atlassian.com/server/jira/platform/webhooks/). | ||
| > - You know how to create **WebHooks in Jira** to enable real-time sync between Jira and Test Management by Testsigma. For more information, see <a href="https://developer.atlassian.com/server/jira/platform/webhooks/" rel="nofollow">Creating WebHooks in Jira</a> |
There was a problem hiding this comment.
Fix markdown linting issues in prerequisites blockquote.
Static analysis flags indentation (MD007) and blockquote spacing (MD027) issues at line 50. The unordered list within the blockquote needs proper alignment—expected 0 indentation but found 3 spaces. Additionally, there are multiple spaces after the blockquote symbol which violates markdown formatting conventions.
Apply this diff to fix the markdown formatting:
> ## **Prerequisites**
>
> Before you begin, ensure:
> - You have a project created in Test Management by Testsigma.
> - The project is connected to a Jira project.
> - You have **Admin Access** in Jira to authorize the initial integration with Test Management by Testsigma.
-~> - You know how to create **WebHooks in Jira** to enable real-time sync between Jira and Test Management by Testsigma. For more information, see <a href="https://developer.atlassian.com/server/jira/platform/webhooks/" rel="nofollow">Creating WebHooks in Jira</a>
+> - You know how to create **WebHooks in Jira** to enable real-time sync between Jira and Test Management by Testsigma. For more information, see <a href="https://developer.atlassian.com/server/jira/platform/webhooks/" rel="nofollow">Creating WebHooks in Jira</a>.Also, note the typo correction from "Jir a" to "Jira" is appreciated.
Committable suggestion skipped: line range outside the PR's diff.
🧰 Tools
🪛 markdownlint-cli2 (0.18.1)
50-50: Unordered list indentation
Expected: 0; Actual: 3
(MD007, ul-indent)
50-50: Multiple spaces after blockquote symbol
(MD027, no-multiple-space-blockquote)
🤖 Prompt for AI Agents
In src/pages/docs/test-management/atto/sprint-planner/manage-sprints.md around
line 50, the prerequisites blockquote has incorrect indentation and extra spaces
after the '>' causing MD007 and MD027 lint errors; remove the three-space
indentation before the list item so the unordered list is flush with the
blockquote marker (no leading spaces), ensure there is exactly one space after
the '>' and that list markers start at column 1 of the blockquote, and verify
the product name is spelled "Jira".
Added no follow links as per SEO team suggestions
Summary by CodeRabbit