Skip to content

chore: add CodeRabbit and mark active development - #11

Merged
eXPerience83 merged 12 commits into
mainfrom
agent/add-coderabbit-development-status
Jul 23, 2026
Merged

chore: add CodeRabbit and mark active development#11
eXPerience83 merged 12 commits into
mainfrom
agent/add-coderabbit-development-status

Conversation

@eXPerience83

@eXPerience83 eXPerience83 commented Jul 23, 2026

Copy link
Copy Markdown
Owner

What changed

  • Add .coderabbit.yaml with focused review instructions for Dockerfiles, Bash, GitHub Actions, Compose and documentation.
  • Use an assertive review profile without automatically blocking merges.
  • Keep automatic reviews limited to non-draft pull requests.
  • Mark the repository and GHCR edge channel clearly as active development / experimental.
  • Update English and Spanish READMEs, changelog, project status, release-channel documentation and roadmap.
  • Document that public availability does not make the web terminal safe to expose directly to the Internet.

Why

The repository and container images are moving to public development so testing can be simpler and CodeRabbit can participate in pull-request reviews. The project must remain explicit that no stable release exists and that TrueNAS, authentication, persistence and sandbox validation are still incomplete.

Validation

  • .coderabbit.yaml parses as valid YAML and uses the current CodeRabbit v2 schema URL.
  • Existing Build AMD64 workflow must pass.
  • After the repository is public and CodeRabbit is installed, request a review on this PR with @coderabbitai review if it does not start automatically.

Use squash merge after CI and the first CodeRabbit review are satisfactory.

Summary by CodeRabbit

  • Nuevas funcionalidades

    • Las imágenes edge ahora están disponibles públicamente para pruebas experimentales.
    • Se incorporan etiquetas inmutables sha-... para facilitar despliegues reproducibles.
    • Se mantiene edge-amd64 para seguir la versión de desarrollo más reciente.
  • Documentación

    • Se actualizan las instrucciones de uso, publicación y pruebas de imágenes edge.
    • Se aclara que el proyecto está en desarrollo experimental y aún no tiene una versión estable.
    • Se añaden advertencias sobre cambios incompatibles y la exposición directa del terminal web a Internet.
    • Se actualizan el estado del proyecto, la hoja de ruta y el registro de cambios.

@qodo-code-review

Copy link
Copy Markdown

Qodo reviews are paused for this user.

Troubleshooting steps vary by plan Learn more →

On a Teams plan?
Reviews resume once this user has a paid seat and their Git account is linked in Qodo.
Link Git account →

Using GitHub Enterprise Server, GitLab Self-Managed, or Bitbucket Data Center?
These require an Enterprise plan - Contact us
Contact us →

@eXPerience83

Copy link
Copy Markdown
Owner Author

@coderabbitai review

@coderabbitai

coderabbitai Bot commented Jul 23, 2026

Copy link
Copy Markdown
✅ Action performed

Review finished.

Note: CodeRabbit is an incremental review system and does not re-review already reviewed commits. This command is applicable only when automatic reviews are paused.

@coderabbitai

coderabbitai Bot commented Jul 23, 2026

Copy link
Copy Markdown

Review Change Stack

Warning

Review limit reached

@eXPerience83, you've reached your PR review limit, so we couldn't start this review.

Next review available in: 52 minutes

Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available.
You're only billed for reviews past your plan's rate limits ($0.25/file).

How can I continue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews.

How do review limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability.

For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window.

Please refer docs for additional details.

Review details
⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro Plus

Run ID: c95f9f57-fa59-49f3-9276-18eca21c7d73

📥 Commits

Reviewing files that changed from the base of the PR and between 55e128e and 67f064c.

📒 Files selected for processing (5)
  • CHANGELOG.md
  • README.es.md
  • README.md
  • docs/releases.md
  • docs/roadmap.md
📝 Walkthrough

Walkthrough

La configuración de CodeRabbit incorpora revisiones automáticas específicas por tipo de archivo. La documentación actualiza el proyecto a un estado experimental con imágenes edge públicas, etiquetas reproducibles, advertencias de seguridad y nuevos hitos de desarrollo.

Changes

Publicación experimental y revisiones

Layer / File(s) Summary
Configuración de CodeRabbit
.coderabbit.yaml
Define el idioma, las revisiones automáticas, las instrucciones para Dockerfiles, Bash, GitHub Actions, Compose y Markdown, además de las respuestas automáticas.
Documentación de imágenes edge
README.md, README.es.md, docs/releases.md
Describe el canal público experimental, el consumo sin autenticación, las etiquetas sha-..., el uso de edge-amd64 y las advertencias sobre ttyd.
Estado, changelog y roadmap
CHANGELOG.md, PROJECT_STATUS.md, docs/roadmap.md
Actualiza el estado experimental, las políticas de publicación, la validación previa al primer lanzamiento estable y los hitos relacionados con CodeRabbit.

Estimated code review effort: 2 (Simple) | ~10 minutes

🚥 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 El título resume bien las dos बदलाव principales: añadir CodeRabbit y marcar el proyecto como desarrollo activo/experimental.
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.

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.

@coderabbitai coderabbitai Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

Actionable comments posted: 1

🧹 Nitpick comments (1)
README.es.md (1)

47-47: 📐 Maintainability & Code Quality | 🔵 Trivial | ⚡ Quick win

Enlaza también docs/releases.md desde el índice en español.

Ese documento contiene los canales de release y las instrucciones de rollback de la imagen pública; el README inglés sí lo incluye, pero esta lista no.

🤖 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.es.md` at line 47, Actualiza el índice de documentación en
README.es.md para incluir también el enlace a docs/releases.md, manteniendo la
lista existente de README.md, PROJECT_STATUS.md, CHANGELOG.md y docs/roadmap.md.
🤖 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 `@docs/releases.md`:
- Line 15: Update the container-image references in docs/releases.md:15,
README.md:63, README.es.md:37-40, CHANGELOG.md:21, and docs/roadmap.md:15 so
they do not claim sha-... tags are immutable unless overwrite protection is
configured; document immutable image digests instead, or revise the wording to
state the required registry/workflow protection while preserving the guidance
for edge-amd64.

---

Nitpick comments:
In `@README.es.md`:
- Line 47: Actualiza el índice de documentación en README.es.md para incluir
también el enlace a docs/releases.md, manteniendo la lista existente de
README.md, PROJECT_STATUS.md, CHANGELOG.md y docs/roadmap.md.
🪄 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 Plus

Run ID: 5f034ee8-5844-4e05-8498-019821a8289a

📥 Commits

Reviewing files that changed from the base of the PR and between efb843e and 55e128e.

📒 Files selected for processing (7)
  • .coderabbit.yaml
  • CHANGELOG.md
  • PROJECT_STATUS.md
  • README.es.md
  • README.md
  • docs/releases.md
  • docs/roadmap.md

Comment thread docs/releases.md Outdated
@eXPerience83
eXPerience83 merged commit 1cf43a8 into main Jul 23, 2026
2 checks passed
@eXPerience83
eXPerience83 deleted the agent/add-coderabbit-development-status branch July 23, 2026 15:29
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