You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
(doc) installation: use https instead of git:// to clone the repository - #3172
Updated the installation instructions to use an HTTPS repository clone command instead of the git:// protocol. Readers following the guide will now use HTTPS when cloning the repository. The change is limited to the documented clone command; the remaining installation guidance is unchanged.
No actionable comments were generated in the recent review. 🎉
ℹ️ Recent review info
⚙️ Run configuration
Source mode: Auto
Repository: Unavailable
Branch: Unavailable
File: No configuration file from this repository applied
Commit: Unavailable
Layers: Repository UI
Review profile: ASSERTIVE
Plan: Advanced
Run ID: b38cd34b-c7be-4d4d-bdf3-b5d4388902ed
📥 Commits
Reviewing files that changed from the base of the PR and between 09066f6 and 61f5b63.
📒 Files selected for processing: 1
doc/src/pgRouting-installation.rst
Included review availability: This review used your included allowance. Your plan provides up to 4 included reviews per hour; 3 remain after this review.
Walkthrough
The installation guide now uses an HTTPS URL in its repository clone command instead of the git:// protocol.
The installation guide uses a supported HTTPS clone URL, with no merge-blocking risk identified.
Pre-merge checks: 5
Check name
Status
Explanation
Description Check
Check skipped - CodeRabbit’s high-level summary is enabled.
Title check
The title clearly and concisely describes the documentation change from the deprecated git:// protocol to HTTPS for repository cloning.
Docstring Coverage
No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check. Docstring coverage is scoped to functions touched by this diff. Analyzed 0 functions across 0…
Linked Issues check
Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check
Check skipped because no linked issues were found for this pull request.
Full details: Docstring Coverage
Explanation
No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check. Docstring coverage is scoped to functions touched by this diff. Analyzed 0 functions across 0 files. (1 skipped: 1 unsupported.)
✨ Finishing Touches
🧪 Generate unit tests (beta)
Create a new PR
Autofix · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts
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.
A rabbit checks the install guide, The clone command takes HTTPS stride. No git:// in the way, A simpler path to start the day. Hop, the guide is up to date!
Comment @coderabbitai help to get the list of available commands.
This branch has not been deployed
No deployments
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Changes proposed in this pull request:
git://github.com/pgRouting/pgrouting.git.git://) in 2022, so the following instruction fails.https://github.com/pgRouting/pgrouting.giton that one line.Tested on macOS 26.6.2: with
git://the clone fails withfatal: unable to connect to github.com; withhttps://the clone succeeds.Before
After
@pgRouting/admins
Summary by CodeRabbit
git://protocol. Readers following the guide will now use HTTPS when cloning the repository. The change is limited to the documented clone command; the remaining installation guidance is unchanged.