Skip to content

Commit 18ce223

Browse files
committed
chore: some rearrange
Signed-off-by: exploreriii <133720349+exploreriii@users.noreply.github.com>
1 parent 119d47a commit 18ce223

1 file changed

Lines changed: 51 additions & 47 deletions

File tree

.github/ISSUE_TEMPLATE/02_good_first_issue.yml

Lines changed: 51 additions & 47 deletions
Original file line numberDiff line numberDiff line change
@@ -20,37 +20,26 @@ body:
2020
label: 🆕🐥 Newcomer Friendly
2121
description: Who is this issue for?
2222
value: |
23-
This **Good First Issue** is a guided, well-scoped task intended for new contributors to the Hiero Python SDK.
23+
This **[Good First Issue](https://github.com/hiero-ledger/hiero-sdk-python/issues?q=is%3Aissue%20state%3Aopen%20label%3A%22Good%20First%20Issue%22%20no%3Aassignee)** is a guided, well-scoped task intended for new contributors to the Hiero Python SDK.
2424
2525
It is designed to help you:
26-
- understand how the repository is structured
27-
- practice the standard contribution workflow
28-
- submit and merge a pull request
29-
30-
No prior knowledge of Hiero, Hedera, or distributed ledger technology is required.
31-
Familiarity with **basic Python** and **Git** is sufficient.
26+
✅ understand how the repository is structured
27+
✅ practice the standard contribution workflow
28+
✅ submit and merge a pull request
3229
3330
A maintainer or mentor actively monitors this issue and will help guide it to completion.
3431
32+
> [!IMPORTANT]
33+
> **This issue does not require prior domain knowledge.**
34+
>
35+
> - No Hiero or Hedera experience needed
36+
> - No distributed ledger background required
37+
> - **Basic Python and Git are sufficient**
38+
3539
⏱️ **Typical time to complete:** 30–90 minutes (once setup is done)
3640
🧩 **Difficulty:** Small, well-contained change
3741
🎓 **Best for:** New contributors
3842
39-
- type: textarea
40-
id: getting_help
41-
attributes:
42-
label: 🧭 Getting help if you’re stuck
43-
description: How to get support while working on this issue.
44-
value: |
45-
If you run into questions or get blocked, don’t spend more than **20 minutes** stuck on your own.
46-
47-
You can:
48-
- comment on this issue and tag `@good_first_issue_support_team` or `@mentor_name`
49-
- ask for help in [Discord](docs/discord.md)
50-
51-
Getting stuck and reaching out for help is a normal part of the contribution process.
52-
Even partial progress or draft pull requests are welcome!
53-
5443
- type: markdown
5544
attributes:
5645
value: |
@@ -321,6 +310,21 @@ body:
321310
validations:
322311
required: true
323312

313+
- type: textarea
314+
id: getting_help
315+
attributes:
316+
label: 🧭 Getting help if you’re stuck
317+
description: How to get support while working on this issue.
318+
value: |
319+
If you run into questions or get blocked, don’t spend more than **20 minutes** stuck on your own.
320+
321+
You can:
322+
- comment on this issue and tag `@good_first_issue_support_team` or `@mentor_name`
323+
- ask for help in [Discord](docs/discord.md)
324+
325+
Getting stuck and reaching out for help is a normal part of the contribution process.
326+
Even partial progress or draft pull requests are welcome!
327+
324328
- type: textarea
325329
id: pr_expectations
326330
attributes:
@@ -350,7 +354,7 @@ body:
350354
351355
#### 😎 Team Member review
352356
A Python SDK team member will review your PR, typically within **1–3 days**.
353-
Reviews focus on clarity and learning, and do not expect perfection.
357+
Reviews focus on clarity and learning.
354358
355359
- You may be asked to make changes, or
356360
- Your PR may be approved as-is ✅
@@ -370,13 +374,33 @@ body:
370374
### 🏁 What success looks like
371375
372376
When this issue is complete, you will have:
373-
✅ Solved a real issue we need resolving
374-
✅ a merged pull request in the Hiero Python SDK
375-
✅ your name permanently in the project history
376-
✅ confidence to take on larger issues next
377+
✅ Solved a real issue we need resolving
378+
✅ a merged pull request in the Hiero Python SDK
379+
✅ your name permanently in the project history
380+
✅ confidence to take on larger issues next
377381
validations:
378382
required: true
379383

384+
- type: textarea
385+
id: ai_usage_guidelines
386+
attributes:
387+
label: 🤖 AI usage guidelines
388+
description: Guidance on using AI tools responsibly for this issue.
389+
value: |
390+
You’re welcome to use AI tools while working on this issue.
391+
392+
Many contributors do — especially for:
393+
- understanding unfamiliar code
394+
- drafting small refactors
395+
- sanity-checking approaches
396+
397+
**Use AI responsibly:**
398+
- review suggestions carefully
399+
- apply changes incrementally
400+
- test as you go
401+
402+
If in doubt, ask — maintainers are happy to help.
403+
380404
- type: textarea
381405
id: information
382406
attributes:
@@ -410,23 +434,3 @@ body:
410434
#### Calls:
411435
- Get hands-on-help by our expert team at our [Office Hours](https://zoom-lfx.platform.linuxfoundation.org/meeting/99912667426?password=5b584a0e-1ed7-49d3-b2fc-dc5ddc888338)
412436
- Learn, raise issues and provide feedback at [Community Calls](https://zoom-lfx.platform.linuxfoundation.org/meeting/92041330205?password=2f345bee-0c14-4dd5-9883-06fbc9c60581)
413-
414-
- type: textarea
415-
id: ai_usage_guidelines
416-
attributes:
417-
label: 🤖 AI usage guidelines
418-
description: Guidance on using AI tools responsibly for this issue.
419-
value: |
420-
You’re welcome to use AI tools while working on this issue.
421-
422-
Many contributors do — especially for:
423-
- understanding unfamiliar code
424-
- drafting small refactors
425-
- sanity-checking approaches
426-
427-
**Use AI responsibly:**
428-
- review suggestions carefully
429-
- apply changes incrementally
430-
- test as you go
431-
432-
If in doubt, ask — maintainers are happy to help.

0 commit comments

Comments
 (0)