|
10 | 10 | attributes: |
11 | 11 | label: 🧠 Advanced Contributors — Prerequisites & Expectations |
12 | 12 | description: | |
13 | | - PRE-FILLED. DO NOT CLAIM THIS ISSUE UNLESS YOU MEET THESE GUIDELINES. |
| 13 | + REQUIRED: Contributors must meet these thresholds before claiming. |
14 | 14 | value: | |
15 | 15 | > [!CAUTION] |
16 | 16 | > **Advanced issues are the highest-risk work in this project. We will reject PRs that do not meet these standards.** |
|
19 | 19 | - **Proven History:** Successfully completed **≥ 10 non-trivial intermediate issues** in this repo. |
20 | 20 | - **Consistency:** **≥ 3–4 months** of active, human-led contributions to this SDK. |
21 | 21 | - **Expertise:** Deep architectural understanding of `_Executable`, `Transaction`, and `Query` base classes. |
| 22 | + - **Advanced Python:** Demonstrated proficiency with complex patterns (e.g., async concurrency, decorators, or state management) used in the core SDK. |
22 | 23 |
|
23 | 24 | > [!NOTE] |
24 | 25 | > **Workflow Exception:** For issues focused on **GitHub Actions / Workflows**, the Python-specific thresholds above may be waived if the contributor demonstrates expert-level proficiency in CI/CD security and automation. |
@@ -72,23 +73,19 @@ body: |
72 | 73 | validations: |
73 | 74 | required: false |
74 | 75 |
|
75 | | - - type: checkboxes |
| 76 | + - type: textarea |
76 | 77 | id: acceptance |
77 | 78 | attributes: |
78 | 79 | label: ✅ PR Quality Checklist |
79 | 80 | description: | |
80 | | - The contributor must manually verify each of these criteria in their Pull Request. |
81 | | - options: |
82 | | - - label: "I understand the system-wide impact of these changes on affected modules and performance." |
83 | | - required: true |
84 | | - - label: "The system design fits with current Hiero SDK architectural approaches." |
85 | | - required: true |
86 | | - - label: "I have tested my changes extensively against both local and network environments." |
87 | | - required: true |
88 | | - - label: "I have verified naming, types, and field ordering against pinned Protobufs (v0.72.0-rc.2)." |
89 | | - required: true |
90 | | - - label: "Every line of code is personally understood and explainable (no unvalidated AI code)." |
91 | | - required: true |
| 81 | + PRE-FILLED. These are the standards the contributor must meet before opening a PR. |
| 82 | + value: | |
| 83 | + Before opening your PR, the contributor must confirm: |
| 84 | + - [ ] I understand the system-wide impact of these changes on affected modules and performance. |
| 85 | + - [ ] The system design fits with current Hiero SDK architectural approaches. |
| 86 | + - [ ] I have tested my changes extensively against both local and network environments. |
| 87 | + - [ ] I have verified naming, types, and field ordering against pinned Protobufs (v0.72.0-rc.2). |
| 88 | + - [ ] Every line of code is personally understood and explainable (no unvalidated AI code). |
92 | 89 |
|
93 | 90 | - type: textarea |
94 | 91 | id: resources |
|
0 commit comments