People are using different linting formats, which leads to wrong recognition in conflicts. Using a common prettier config can help everyone to be on the same page and reduce merge conflict rates due to meta.json, etc.
Originally created by @vlhsmylv on GitHub (Jul 7, 2025).
Original GitHub issue: https://github.com/Dokploy/templates/issues/216
People are using different linting formats, which leads to wrong recognition in conflicts. Using a common prettier config can help everyone to be on the same page and reduce merge conflict rates due to `meta.json`, etc.
The main pain behind this (merge conflicts in the giant root meta.json) was eliminated in #978 — metadata now lives per-template in blueprints//meta.json, so cross-PR conflicts can no longer happen. A repo-wide prettier config is not planned for now.
<!-- gh-comment-id:4971726409 -->
@Siumauricio commented on GitHub (Jul 14, 2026):
The main pain behind this (merge conflicts in the giant root meta.json) was eliminated in #978 — metadata now lives per-template in blueprints/<id>/meta.json, so cross-PR conflicts can no longer happen. A repo-wide prettier config is not planned for now.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Originally created by @vlhsmylv on GitHub (Jul 7, 2025).
Original GitHub issue: https://github.com/Dokploy/templates/issues/216
People are using different linting formats, which leads to wrong recognition in conflicts. Using a common prettier config can help everyone to be on the same page and reduce merge conflict rates due to
meta.json, etc.@Siumauricio commented on GitHub (Jul 14, 2026):
The main pain behind this (merge conflicts in the giant root meta.json) was eliminated in #978 — metadata now lives per-template in blueprints//meta.json, so cross-PR conflicts can no longer happen. A repo-wide prettier config is not planned for now.