Skip to content

docs: point the documentation link at commit-check.com - #43

Closed
shenxianpeng wants to merge 1 commit into
mainfrom
docs/point-links-at-commit-check-com
Closed

docs: point the documentation link at commit-check.com#43
shenxianpeng wants to merge 1 commit into
mainfrom
docs/point-links-at-commit-check-com

Conversation

@shenxianpeng

@shenxianpeng shenxianpeng commented Aug 4, 2026

Copy link
Copy Markdown
Member

The documentation moved to commit-check/commit-check.com, where the apex domain now carries the landing page, the blog and the documentation together.

Updates the one link in profile/README.md:

  • docs.commit-check.comcommit-check.com

This is the organisation profile page, so it is the most visible of the links being updated in this migration. The Website badge just above it already pointed at commit-check.com, so the two now agree.


Generated by Claude Code

Summary by CodeRabbit

  • Documentation
    • Updated the README documentation link to point to the current website.

The documentation moved to its own repository and is served from the apex
domain, which now carries the landing page, the blog and the docs together.
@coderabbitai

coderabbitai Bot commented Aug 4, 2026

Copy link
Copy Markdown

Review Change Stack

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info
⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro Plus

Run ID: 1721e7f5-c13e-4c3a-9da5-b3aeeda7c8e6

📥 Commits

Reviewing files that changed from the base of the PR and between f298e6c and 64d995f.

📒 Files selected for processing (1)
  • profile/README.md

📝 Walkthrough

Walkthrough

The profile README now links Documentation to https://commit-check.com instead of https://docs.commit-check.com.

Changes

Documentation Link

Layer / File(s) Summary
Update Documentation link
profile/README.md
The Documentation link now points to https://commit-check.com.

Estimated code review effort: 1 (Trivial) | ~2 minutes

Possibly related PRs

Suggested labels: documentation

🚥 Pre-merge checks | ✅ 5
✅ Passed checks (5 passed)
Check name Status Explanation
Description Check ✅ Passed Check skipped - CodeRabbit’s high-level summary is enabled.
Title check ✅ Passed The title clearly and concisely describes the documentation link update to commit-check.com.
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check ✅ Passed Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check ✅ Passed Check skipped because no linked issues were found for this pull request.
✨ Finishing Touches 💡 1
🛠️ Fix failing CI checks 💡
  • Create stacked PR
  • Commit on current branch
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch docs/point-links-at-commit-check-com

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.

@github-actions

github-actions Bot commented Aug 4, 2026

Copy link
Copy Markdown

Commit-Check ❌

--- PR Title:
Type subject_imperative check failed ==> docs: point the documentation link at commit-check.com 
Commit message should use imperative mood (e.g., 'fix bug' not 'fixed bug', 'add feature' not 'adding feature')
Suggest: Change the first verb to imperative form, e.g., 'fix' instead of 'fixed'/'fixes'/'fixing' 

--- Commit 1/1:
Type subject_imperative check failed ==> docs: point the documentation link at commit-check.com 
Commit message should use imperative mood (e.g., 'fix bug' not 'fixed bug', 'add feature' not 'adding feature')
Suggest: Change the first verb to imperative form, e.g., 'fix' instead of 'fixed'/'fixes'/'fixing' 
Commit rejected by Commit-Check.                                  
                                                                  
  (c).-.(c)    (c).-.(c)    (c).-.(c)    (c).-.(c)    (c).-.(c)  
   / ._. \      / ._. \      / ._. \      / ._. \      / ._. \   
 __\( C )/__  __\( H )/__  __\( E )/__  __\( C )/__  __\( K )/__ 
(_.-/'-'\-._)(_.-/'-'\-._)(_.-/'-'\-._)(_.-/'-'\-._)(_.-/'-'\-._)
   || E ||      || R ||      || R ||      || O ||      || R ||   
 _.' '-' '._  _.' '-' '._  _.' '-' '._  _.' '-' '._  _.' '-' '._ 
(.-./`-´\.-.)(.-./`-´\.-.)(.-./`-´\.-.)(.-./`-´\.-.)(.-./`-´\.-.)
 `-´     `-´  `-´     `-´  `-´     `-´  `-´     `-´  `-´     `-´ 
                                                                  
Commit rejected.                                                  
                                                                  
Type branch check failed ==> docs/point-links-at-commit-check-com 
The branch should follow Conventional Branch. See https://conventionalbranch.org
Suggest: Use <type>/<description> with allowed types or add branch name to allow_branch_names in config, or use ignore_authors in config branch section to bypass

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.

1 participant