[PR #736] docs: updates for PR #730 #2056

New Issue

GiteaMirror · 2026-04-20T11:04:38-05:00

GiteaMirror commented

2026-04-20 11:04:38 -05:00

📋 Pull Request Information

Original PR: https://github.com/Dokploy/templates/pull/736
Author: @dosubot[bot]
Created: 3/5/2026
Status: 🔄 Open

Base: canary ← Head: dosu/doc-update-730

📝 Commits (1)

92020b2 docs: Dosu updates for PR #730

📊 Changes

1 file changed (+7 additions, -4 deletions)

View changed files

📝 .github/copilot-instructions.md (+7 -4)

📄 Description

Update documentation for https://github.com/Dokploy/templates/pull/730

Generated by Dosu

Greptile Summary

This PR updates .github/copilot-instructions.md to clarify the port-mapping policy introduced in PR #730: blueprints must use expose instead of ports with host mappings, and this is now stated explicitly ("NEVER use ports with host port mappings") in three places—the key files section, the development workflow, and the conventions section.

The changes are internally consistent and align with the existing AGENTS.md guidance (line 150: "NEVER include: ports (use expose only)").
The expanded Conventions section now explains why host port bindings are prohibited (Dokploy's internal reverse proxy handles routing) and notes that older templates may still incorrectly use ports.
One inaccuracy found: line 27 states the exemplary Ghost blueprint's docker-compose.yml "uses expose: ["2368"] for port exposure", but blueprints/ghost/docker-compose.yml contains no expose directive at all—Ghost's port is handled entirely via template.toml's domain configuration. Since this line is labelled as the reference example for AI agents, the inaccuracy should be corrected.

Confidence Score: 4/5

Documentation-only PR that is safe to merge after fixing a factual inaccuracy in the exemplary blueprint description.
Only one file is changed and the changes are documentation. The core guidance is correct and consistent with AGENTS.md. A single factual inaccuracy (claiming Ghost's docker-compose.yml uses expose: ["2368"] when it does not) lowers the score slightly because this file serves as an AI collaboration guide and inaccurate examples can mislead generated blueprints.
.github/copilot-instructions.md — line 27 contains an inaccurate claim about the Ghost blueprint's use of expose.

_{Last reviewed commit: 92020b2}

Greptile also left 1 inline comment on this PR.

_{(4/5) You can add custom instructions or style guidelines for the agent here!}

_{🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.}

## 📋 Pull Request Information **Original PR:** https://github.com/Dokploy/templates/pull/736 **Author:** [@dosubot[bot]](https://github.com/apps/dosubot) **Created:** 3/5/2026 **Status:** 🔄 Open **Base:** `canary` ← **Head:** `dosu/doc-update-730` --- ### 📝 Commits (1) - [`92020b2`](https://github.com/Dokploy/templates/commit/92020b2e2deb7000c45f5d4001a8ae55ffdc1538) docs: Dosu updates for PR #730 ### 📊 Changes **1 file changed** (+7 additions, -4 deletions) <details> <summary>View changed files</summary> 📝 `.github/copilot-instructions.md` (+7 -4) </details> ### 📄 Description Update documentation for https://github.com/Dokploy/templates/pull/730 _Generated by [Dosu](https://dosu.dev)_  <h3>Greptile Summary</h3> This PR updates `.github/copilot-instructions.md` to clarify the port-mapping policy introduced in PR #730: blueprints must use `expose` instead of `ports` with host mappings, and this is now stated explicitly ("NEVER use `ports` with host port mappings") in three places—the key files section, the development workflow, and the conventions section. - The changes are internally consistent and align with the existing `AGENTS.md` guidance (line 150: "NEVER include: `ports` (use `expose` only)"). - The expanded Conventions section now explains *why* host port bindings are prohibited (Dokploy's internal reverse proxy handles routing) and notes that older templates may still incorrectly use `ports`. - **One inaccuracy found**: line 27 states the exemplary Ghost blueprint's `docker-compose.yml` "uses `expose: ["2368"]` for port exposure", but `blueprints/ghost/docker-compose.yml` contains no `expose` directive at all—Ghost's port is handled entirely via `template.toml`'s domain configuration. Since this line is labelled as the reference example for AI agents, the inaccuracy should be corrected. <h3>Confidence Score: 4/5</h3> - Documentation-only PR that is safe to merge after fixing a factual inaccuracy in the exemplary blueprint description. - Only one file is changed and the changes are documentation. The core guidance is correct and consistent with AGENTS.md. A single factual inaccuracy (claiming Ghost's docker-compose.yml uses `expose: ["2368"]` when it does not) lowers the score slightly because this file serves as an AI collaboration guide and inaccurate examples can mislead generated blueprints. - .github/copilot-instructions.md — line 27 contains an inaccurate claim about the Ghost blueprint's use of `expose`. <sub>Last reviewed commit: 92020b2</sub> > Greptile also left **1 inline comment** on this PR. <sub>(4/5) You can add custom instructions or style guidelines for the agent [here](https://app.greptile.com/review/github)!</sub>  --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>

GiteaMirror added the pull-request label 2026-04-20 11:04:38 -05:00

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: github-starred/templates#2056