|
| 1 | +name: Copilot Issue |
| 2 | +description: Create an issue to be assigned to GitHub Copilot for automated resolution. |
| 3 | +title: "[Copilot] " |
| 4 | +labels: ["copilot"] |
| 5 | +body: |
| 6 | + - type: markdown |
| 7 | + attributes: |
| 8 | + value: | |
| 9 | + ## Copilot Issue Instructions |
| 10 | +
|
| 11 | + This issue will be assigned to GitHub Copilot for automated resolution. Please provide clear information about the changes needed. |
| 12 | +
|
| 13 | + **Note**: Copilot will follow the guidelines in the [CONTRIBUTING.md](../../CONTRIBUTING.md) file. In case of any conflicts between the guidelines in this template and the CONTRIBUTING.md file, the CONTRIBUTING.md file takes precedence. |
| 14 | +
|
| 15 | + - type: textarea |
| 16 | + id: description |
| 17 | + attributes: |
| 18 | + label: Issue Description |
| 19 | + description: Clearly describe what needs to be changed or fixed. |
| 20 | + placeholder: Describe the problem or feature request in detail. |
| 21 | + validations: |
| 22 | + required: true |
| 23 | + |
| 24 | + - type: textarea |
| 25 | + id: expected_changes |
| 26 | + attributes: |
| 27 | + label: Expected Changes |
| 28 | + description: Describe what changes you expect Copilot to make. |
| 29 | + placeholder: List the specific changes you want to see implemented. |
| 30 | + validations: |
| 31 | + required: true |
| 32 | + |
| 33 | + - type: markdown |
| 34 | + attributes: |
| 35 | + value: | |
| 36 | + ## Guidelines for Copilot |
| 37 | +
|
| 38 | + The following guidelines, along with those in the [CONTRIBUTING.md](../../CONTRIBUTING.md) file, will be included in every Copilot issue: |
| 39 | +
|
| 40 | + ### Documentation Requirements |
| 41 | + - Document all changes made in your PR description in a clear and concise manner |
| 42 | + - Update existing repository documentation files if the changes affect documented behavior |
| 43 | + - Include code comments for complex logic when necessary |
| 44 | +
|
| 45 | + ### Coding Standards |
| 46 | + - Stick strictly to the existing coding conventions in this repository |
| 47 | + - Follow established Go language practices and conventions: |
| 48 | + - Use proper error handling patterns |
| 49 | + - Follow Go naming conventions (e.g., CamelCase for exported names) |
| 50 | + - Write concise, readable code with appropriate comments |
| 51 | + - Use Go idioms and standard library functions where appropriate |
| 52 | + - Organize imports according to Go best practices |
| 53 | + - Ensure code passes golangci-lint checks |
| 54 | +
|
| 55 | + ### Quality Standards |
| 56 | + - Make minimal, focused changes to achieve the required functionality |
| 57 | + - Write or update tests for new or modified code |
| 58 | + - Ensure backward compatibility unless explicitly instructed otherwise |
| 59 | + - Follow programming best practices: |
| 60 | + - Keep functions small and focused on a single task |
| 61 | + - Use appropriate error handling |
| 62 | + - Avoid code duplication |
| 63 | + - Use meaningful variable and function names |
| 64 | +
|
| 65 | + - type: textarea |
| 66 | + id: additional_context |
| 67 | + attributes: |
| 68 | + label: Additional Context |
| 69 | + description: Any additional information that might help Copilot complete the task. |
| 70 | + placeholder: Include links to related code, examples, or other resources that might help. |
| 71 | + validations: |
| 72 | + required: false |
0 commit comments