Skip to content

add shared instruction for copilot usage #22254

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
cedric-anne merged 5 commits into from
Dec 9, 2025
Merged

add shared instruction for copilot usage #22254

Changes from 4 commits
Commits
Show all changes
5 commits
Select commit Hold shift + click to select a range
6d7c1ed
add shared instruction for copilot usage
orthagh Dec 5, 2025
94d5283
Update .github/copilot-instructions.md
orthagh Dec 5, 2025
a3911c4
front files and libraries
orthagh Dec 5, 2025
91b46bf
Update .github/copilot-instructions.md
orthagh Dec 5, 2025
2e3d7be
Update .github/copilot-instructions.md
orthagh Dec 9, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
16 changes: 16 additions & 0 deletions .github/copilot-instructions.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1,16 @@
Follow GLPI’s latest coding standards and best practices: naming, indentation, comments, and PER Coding Style 3.0 compliance.
Use the GLPI framework whenever possible.
Do not use deprecated code.
Do not use PHP features older than version 8.2.
Do not use GLPI code or APIs older than version 10.0.
Never create .md or .txt files to explain changes.
Never explain what you did.
Do not add unnecessary comments or TODO notes.
Follow the MVC pattern, routing, and controllers wherever possible.
Do not create /front/ files — always use controllers and routes if possible.
Never output raw HTML with echo; always use Twig templates.
Never execute raw SQL — always use GLPI’s ORM and database abstraction layer.
Do not ask clarification questions, except when a real choice between two technical solutions must be made.
Do not generate tests unless requested.
When generating code, always ensure it is secure and free from vulnerabilities.
When importing libraries or packages, prefer already imported ones; if using new ones, they must be compatible with GLPI GPLv3+ License.