Skip to content

Conversation

@Fawas003
Copy link
Contributor

@Fawas003 Fawas003 commented Oct 17, 2025

fixed broken link in bhashini integration page

Summary by CodeRabbit

  • Documentation
    • Updated resource links in the Bhashini integration guide to reference the current documentation structure.

fixed broken link in bhashini integration page
@Fawas003 Fawas003 requested a review from mahajantejas October 17, 2025 09:45
@coderabbitai
Copy link
Contributor

coderabbitai bot commented Oct 17, 2025

Walkthrough

Two Google Cloud Storage setup links were updated in the Bhashini integration documentation. The link targets changed from the Onboarding directory path to the Pre Onboarding directory path, reflecting a documentation structure reorganization.

Changes

Cohort / File(s) Change Summary
Documentation Link Updates
docs/5. Integrations/Bhashini Integrations.md
Updated two GCS setup link references from Onboarding path (/docs/Onboarding/GCS Setup/Google Cloud Storage Setup/) to Pre Onboarding path (/docs/Pre Onboarding/Google Cloud Storage Setup - GCS)

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Possibly related PRs

  • glific/docs#469: Updates the same Google Cloud Storage setup link from Onboarding to Pre Onboarding path structure.
  • glific/docs#394: Modifies Bhashini integration documentation's Google Cloud Storage setup link target URL.
  • glific/docs#446: Updates links to point to GCS Setup documentation in the Pre Onboarding location.

Suggested reviewers

  • mahajantejas
  • SangeetaMishr

Poem

🐰 Links hop from old paths to new,
Through Pre Onboarding meadows they flew,
Two breadcrumbs corrected with care,
Bhashini's setup now leads you there!

Pre-merge checks and finishing touches

❌ Failed checks (1 inconclusive)
Check name Status Explanation Resolution
Title Check ❓ Inconclusive The title "Update Bhashini Integrations.md" is vague and uses generic terminology that lacks specificity about the actual change. While it correctly identifies the file being modified, it fails to convey the meaningful intent of the pull request — specifically, that this is a fix for broken links in the Bhashini integration documentation. A reader scanning the commit history would not immediately understand why the file was updated or what problem was being addressed. Consider revising the title to be more descriptive and specific, such as "Fix broken Google Cloud Storage links in Bhashini integration" or "Update GCS setup links in Bhashini integration guide". This would clearly communicate the primary change (fixing broken links) and help team members quickly understand the purpose of the update.
✅ Passed checks (2 passed)
Check name Status Explanation
Description Check ✅ Passed Check skipped - CodeRabbit’s high-level summary is enabled.
Docstring Coverage ✅ Passed No functions found in the changes. Docstring coverage check skipped.
✨ Finishing touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Post copyable unit tests in a comment
  • Commit unit tests in branch fixbrokenlink---Bhashini-Integration

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 and usage tips.

@github-actions
Copy link

@github-actions github-actions bot temporarily deployed to pull request October 17, 2025 09:46 Inactive
Copy link
Contributor

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

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

Actionable comments posted: 0

🧹 Nitpick comments (1)
docs/5. Integrations/Bhashini Integrations.md (1)

105-105: Improve link text descriptiveness and phrasing conciseness.

Two minor improvements on this line:

  1. The link text "click here" is generic and doesn't clearly describe the link destination. Use descriptive text that indicates the user is setting up Google Cloud Storage.
  2. The phrase "In order to" is verbose; "To" is more concise.

Apply this diff to improve readability and accessibility:

-Please note: In order to get the voice notes as outputs, the Glific instance must be linked to the Google Cloud Storage for your organization. This is to facilitate storage of the voice notes generated by Bhashini as a result of the webhook call. To set up Google Cloud Storage [click here](https://glific.github.io/docs/docs/Pre%20Onboarding/Google%20Cloud%20Storage%20Setup%20-%20GCS)
+Please note: To get the voice notes as outputs, the Glific instance must be linked to the Google Cloud Storage for your organization. This is to facilitate storage of the voice notes generated by Bhashini as a result of the webhook call. See [Google Cloud Storage setup documentation](https://glific.github.io/docs/docs/Pre%20Onboarding/Google%20Cloud%20Storage%20Setup%20-%20GCS).
📜 Review details

Configuration used: CodeRabbit UI

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 0a9b775 and 15bc1b9.

📒 Files selected for processing (1)
  • docs/5. Integrations/Bhashini Integrations.md (1 hunks)
🧰 Additional context used
🪛 LanguageTool
docs/5. Integrations/Bhashini Integrations.md

[style] ~105-~105: Consider a more concise word here.
Context: ...944-ab5f-b929b52ce5fc" /> Please note: In order to get the voice notes as outputs, the Gli...

(IN_ORDER_TO_PREMIUM)

🪛 markdownlint-cli2 (0.18.1)
docs/5. Integrations/Bhashini Integrations.md

105-105: Link text should be descriptive

(MD059, descriptive-link-text)

🔇 Additional comments (1)
docs/5. Integrations/Bhashini Integrations.md (1)

1-135: Review comment is incorrect—there is only one GCS link, not two.

The file contains a single Google Cloud Storage setup link at line 105, not the two occurrences referenced in the review comment. The one link present (https://glific.github.io/docs/docs/Pre%20Onboarding/Google%20Cloud%20Storage%20Setup%20-%20GCS) is correctly formatted and accessible.

Likely an incorrect or invalid review comment.

@mahajantejas mahajantejas merged commit dabddcc into main Oct 24, 2025
7 checks passed
@mahajantejas mahajantejas deleted the fixbrokenlink---Bhashini-Integration branch October 24, 2025 08:34
@coderabbitai coderabbitai bot mentioned this pull request Oct 24, 2025
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.

3 participants