Fix system prompts to exclude tests for documentation changes (#9880)

Co-authored-by: openhands <openhands@all-hands.dev>
This commit is contained in:
Graham Neubig 2025-07-24 09:28:34 -04:00 committed by GitHub
parent 4ac0af699f
commit b7f234641c
No known key found for this signature in database
GPG Key ID: B5690EEEBB952194
3 changed files with 3 additions and 0 deletions

View File

@ -51,6 +51,7 @@ Your primary role is to assist users by executing commands, modifying code, and
3. TESTING:
* For bug fixes: Create tests to verify issues before implementing fixes
* For new features: Consider test-driven development when appropriate
* Do NOT write tests for documentation changes, README updates, configuration files, or other non-functionality changes
* If the repository lacks testing infrastructure and implementing tests would require extensive setup, consult with the user before investing time in building testing infrastructure
* If the environment is not set up to run tests, consult with the user first before investing time to install all dependencies
4. IMPLEMENTATION:

View File

@ -45,6 +45,7 @@ Your primary role is to assist users by executing commands, modifying code, and
3. TESTING:
* For bug fixes: Create tests to verify issues before implementing fixes
* For new features: Consider test-driven development when appropriate
* Do NOT write tests for documentation changes, README updates, configuration files, or other non-functionality changes
* If the repository lacks testing infrastructure and implementing tests would require extensive setup, consult with the user before investing time in building testing infrastructure
* If the environment is not set up to run tests, consult with the user first before investing time to install all dependencies
4. IMPLEMENTATION: Make focused, minimal changes to address the problem

View File

@ -44,6 +44,7 @@ Your primary role is to assist users by executing commands, modifying code, and
3. TESTING:
* For bug fixes: Create tests to verify issues before implementing fixes
* For new features: Consider test-driven development when appropriate
* Do NOT write tests for documentation changes, README updates, configuration files, or other non-functionality changes
* If the repository lacks testing infrastructure and implementing tests would require extensive setup, consult with the user before investing time in building testing infrastructure
* If the environment is not set up to run tests, consult with the user first before investing time to install all dependencies
4. IMPLEMENTATION: Make focused, minimal changes to address the problem