Skip to content

docs: refresh README (AI-assisted)#942

Open
igorpecovnik wants to merge 1 commit into
mainfrom
chore/update-readme
Open

docs: refresh README (AI-assisted)#942
igorpecovnik wants to merge 1 commit into
mainfrom
chore/update-readme

Conversation

@igorpecovnik

@igorpecovnik igorpecovnik commented Jul 20, 2026

Copy link
Copy Markdown
Member

Automated README refresh generated by the Maintenance: Update README (AI)
workflow in armbian.github.io.

The content is generated by Claude from this repository's own files (file tree,
manifests, workflows, existing README). Please review for accuracy before
merging — edit or close if anything is wrong. Re-running the workflow refreshes
this branch.

Create docs preview on PR

Documentation website preview will be available shortly:


 Open WWW preview 

@github-actions github-actions Bot added size/medium PR with more then 50 and less then 250 lines Needs review Seeking for review labels Jul 20, 2026
@coderabbitai

coderabbitai Bot commented Jul 20, 2026

Copy link
Copy Markdown
Contributor

Review Change Stack

Walkthrough

README.md was rewritten as a structured index for the Armbian Documentation repository. It now covers the repository layout, contribution and file-naming guidance, local MkDocs setup and serving, documentation tooling, GitHub Actions automation, and the GPL v3 license. The header also adds branding, workflow badges, and links to published documentation and PDF outputs.

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

🚥 Pre-merge checks | ✅ 5
✅ Passed checks (5 passed)
Check name Status Explanation
Title check ✅ Passed The title clearly and concisely summarizes the README refresh and AI-assisted nature of the change.
Description check ✅ Passed The description directly matches the automated README update and explains its workflow-based origin and review expectations.
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
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch chore/update-readme

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 Bot pushed a commit that referenced this pull request Jul 20, 2026

@coderabbitai coderabbitai Bot left a comment

Copy link
Copy Markdown
Contributor

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 `@README.md`:
- Around line 24-33: Specify a language on both fenced code blocks in the README
repository-tree examples, including the additional fence around lines 43–45. Use
text or another appropriate language identifier while preserving the existing
contents.
- Around line 94-99: Update the README’s mkdocs serve command to bind the local
preview to 127.0.0.1:8000 instead of 0.0.0.0:8000, and mention the broader
0.0.0.0 binding only as an intentional option for remote access.
- Around line 41-47: Update the argparse help text in tools/mkArmbianDocs.py to
describe the parser’s underscore-separated filename convention, using the
[Parent-Topic]_[Child-Topic]-example.md format instead of
[ParentCategory]-Subtopic.md. Keep the README convention and parser behavior
unchanged.
🪄 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: 7b2b4202-58f4-4533-9f92-077004980fbc

📥 Commits

Reviewing files that changed from the base of the PR and between b36bfe8 and a2f22aa.

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

Comment thread README.md
Comment on lines +24 to +33
```
docs/ Markdown content, images, and CSS
images/ Screenshots and diagrams
css/ Custom stylesheets
overrides/ Theme overrides (main.html)
tools/ Helper scripts (mkArmbianDocs.py)
.github/ Workflows, labels, PR/issue templates
mkdocs.yml MkDocs site configuration
requirements.txt Python dependencies
```

Copy link
Copy Markdown
Contributor

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

Specify languages for fenced code blocks.

Add text (or another appropriate language) to both fences to satisfy Markdown linting and improve rendered documentation.

Proposed fix
-```
+```text
 ...
-```
+```

Also applies to: 43-45

🧰 Tools
🪛 markdownlint-cli2 (0.23.0)

[warning] 24-24: Fenced code blocks should have a language specified

(MD040, fenced-code-language)

🤖 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 `@README.md` around lines 24 - 33, Specify a language on both fenced code
blocks in the README repository-tree examples, including the additional fence
around lines 43–45. Use text or another appropriate language identifier while
preserving the existing contents.

Source: Linters/SAST tools

Comment thread README.md
Comment on lines +41 to +47
### File naming convention

```
[Parent-Topic]_[Child-Topic]-example.md
```

Parent and child topics are separated by an underscore (`_`). Hyphens (`-`) are automatically converted to spaces when rendered. Please avoid creating new parent topics unless absolutely necessary.

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

🗄️ Data Integrity & Integration | 🟡 Minor | ⚡ Quick win

🧩 Analysis chain

🏁 Script executed:

#!/bin/bash
rg -n 'ParentCategory|Parent-Topic|split|findFiles|parseFiles' README.md tools/mkArmbianDocs.py

Repository: armbian/documentation

Length of output: 657


🏁 Script executed:

#!/bin/bash
set -euo pipefail

printf '\n== README excerpt ==\n'
sed -n '38,50p' README.md

printf '\n== tools/mkArmbianDocs.py excerpt ==\n'
nl -ba tools/mkArmbianDocs.py | sed -n '1,120p'

Repository: armbian/documentation

Length of output: 659


🏁 Script executed:

#!/bin/bash
set -euo pipefail

nl -ba tools/mkArmbianDocs.py | sed -n '1,120p'

Repository: armbian/documentation

Length of output: 199


🏁 Script executed:

#!/bin/bash
set -euo pipefail

printf '\n== tools/mkArmbianDocs.py (1-240) ==\n'
awk '{printf "%4d %s\n", NR, $0}' tools/mkArmbianDocs.py | sed -n '1,240p'

printf '\n== search for filename handling ==\n'
grep -nE 'split|replace|Parent|Child|Category|Subtopic|example' tools/mkArmbianDocs.py

Repository: armbian/documentation

Length of output: 7411


Align the generator help text with the parser contract. tools/mkArmbianDocs.py already accepts underscore-separated names like [Parent-Topic]_[Child-Topic]-example.md; the argparse description still says [ParentCategory]-Subtopic.md, which is misleading for contributors.

🧰 Tools
🪛 markdownlint-cli2 (0.23.0)

[warning] 43-43: Fenced code blocks should have a language specified

(MD040, fenced-code-language)

🤖 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 `@README.md` around lines 41 - 47, Update the argparse help text in
tools/mkArmbianDocs.py to describe the parser’s underscore-separated filename
convention, using the [Parent-Topic]_[Child-Topic]-example.md format instead of
[ParentCategory]-Subtopic.md. Keep the README convention and parser behavior
unchanged.

Comment thread README.md
Comment on lines 94 to +99
```bash
mkdocs build --clean
mkdocs serve -a 0.0.0.0:8000
```

Then open your browser and go to http://localhost:8000
The site will automatically reload when you make changes to .md files.
Then open [http://localhost:8000](http://localhost:8000). The site auto-reloads when `.md` files change.

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

🔒 Security & Privacy | 🟡 Minor | ⚡ Quick win

Bind the local preview to localhost by default.

0.0.0.0:8000 exposes unpublished documentation to every reachable network interface. Use 127.0.0.1:8000 for a local-preview instruction, and document the broader bind only for intentional remote access.

Proposed fix
-mkdocs serve -a 0.0.0.0:8000
+mkdocs serve -a 127.0.0.1:8000
📝 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
```bash
mkdocs build --clean
mkdocs serve -a 0.0.0.0:8000
```
Then open your browser and go to http://localhost:8000
The site will automatically reload when you make changes to .md files.
Then open [http://localhost:8000](http://localhost:8000). The site auto-reloads when `.md` files change.
🤖 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 `@README.md` around lines 94 - 99, Update the README’s mkdocs serve command to
bind the local preview to 127.0.0.1:8000 instead of 0.0.0.0:8000, and mention
the broader 0.0.0.0 binding only as an intentional option for remote access.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

documentation Needs review Seeking for review size/medium PR with more then 50 and less then 250 lines

Development

Successfully merging this pull request may close these issues.

1 participant