|
27 | 27 | - Hiero or Hedera |
28 | 28 | - distributed ledger technology |
29 | 29 |
|
30 | | - If you’re comfortable with **basic Python** and **Git**, you’re ready to get started. |
| 30 | + If you have **basic Python** and **Git**, you’re ready to get started. |
31 | 31 |
|
32 | 32 | - type: markdown |
33 | 33 | attributes: |
@@ -229,7 +229,7 @@ body: |
229 | 229 |
|
230 | 230 | - [ ] **Connect** origin with upstream: [Guide](docs/sdk_developers/training/workflow/03_staying_in_sync.md) |
231 | 231 |
|
232 | | - - [ ] **Install Packages** Install packages and protobuffs: [Guide](docs/sdk_developers/training/setup/02_installing_hiero_python_sdk.md) |
| 232 | + - [ ] **Install Packages** and protobuffs: [Guide](docs/sdk_developers/training/setup/02_installing_hiero_python_sdk.md) |
233 | 233 |
|
234 | 234 | - [ ] **Sync Main** pull any recent upstream changes: [Guide](docs/sdk_developers/rebasing.md) |
235 | 235 |
|
@@ -266,7 +266,9 @@ body: |
266 | 266 |
|
267 | 267 | - [ ] **Open a pull request:** [here](https://github.com/hiero-ledger/hiero-sdk-python/pulls) [guide](docs/sdk_developers/training/workflow/11_submit_pull_request.md) |
268 | 268 |
|
269 | | - - [ ] **Complete the PR description:** briefly describe your changes and link the issue, [Guide](docs/sdk_developers/training/workflow/11_submit_pull_request.md) |
| 269 | + - [ ] **Complete the PR description:** briefly describe your changes, [Guide](docs/sdk_developers/training/workflow/11_submit_pull_request.md) |
| 270 | +
|
| 271 | + - [ ] **Link the Issue:** link the issue the PR solves in the PR description, [Guide](docs/sdk_developers/how_to_link_issues.md) |
270 | 272 |
|
271 | 273 | - [ ] **Submit the pull request:** click `**Create pull request**` 🎉 |
272 | 274 |
|
@@ -316,10 +318,10 @@ body: |
316 | 318 | - point out potential issues |
317 | 319 | - suggest improvements or alternatives |
318 | 320 |
|
319 | | - AI feedback is **advisory** — it can make mistakes - use what’s helpful and feel free to ask questions. |
| 321 | + AI feedback is **advisory** — it can make mistakes - use what’s helpful and relevant to the issue description. |
320 | 322 |
|
321 | 323 |
|
322 | | - #### 👀 Maintainer review |
| 324 | + #### 😎 Team Member review |
323 | 325 | A Python SDK team member will review your PR, typically within **1–3 days**. |
324 | 326 | - You may be asked to make changes, or |
325 | 327 | - Your PR may be approved as-is ✅ |
|
0 commit comments