refactor: standardize Good First Issue label usage

Signed-off-by: Bhuvan Somisetty <somisettybhuvan5@gmail.com>

Author: bhuvan-somisetty

.github/ISSUE_TEMPLATE/00-good-first-issue-candidate.yml

@@ -82,7 +82,7 @@ body:
         - The complete steps to implement the solution
         - What the final result or output should look like
         - Links to relevant documentation or code (if helpful)
-        For good first issues, please keep this as guided and clear as possible.
+        For Good First Issues, please keep this as guided and clear as possible.
       value: |
         <!-- Identify what to change in which files -->
 
@@ -95,7 +95,7 @@ body:
     attributes:
       label: 🧠 Good First Issue Developers — Prerequisites & Expectations
       description: |
-        Adapt as needed. Concrete requirements before claiming this good first issue. Adapt as needed.
+        Adapt as needed. Concrete requirements before claiming this Good First Issue. Adapt as needed.
       value: |
         > [!IMPORTANT]
         > **This issue does not require prior domain knowledge.**

.github/ISSUE_TEMPLATE/01-good-first-issue.yml

@@ -69,7 +69,7 @@ body:
         - The complete steps to implement the solution
         - What the final result or output should look like
         - Links to relevant documentation or code (if helpful)
-        For good first issues, please keep this as guided and clear as possible.
+        For Good First Issues, please keep this as guided and clear as possible.
       value: |
         <!-- Identify what to change in which files -->
 
@@ -82,7 +82,7 @@ body:
     attributes:
       label: 🧠 Good First Issue Developers — Prerequisites & Expectations
       description: |
-        Adapt as needed. Concrete requirements before claiming this good first issue. Adapt as needed.
+        Adapt as needed. Concrete requirements before claiming this Good First Issue. Adapt as needed.
       value: |
         > [!IMPORTANT]
         > **This issue does not require prior domain knowledge.**

.github/ISSUE_TEMPLATE/02-beginner-issue.yml

@@ -98,7 +98,7 @@ body:
         > **Beginner issues are low-risk but we expect a working solution.**
 
         > [!IMPORTANT]
-        > We recommend completing at least 3 good first issues before attempting a beginner issue.
+        > We recommend completing at least 3 Good First Issues before attempting a beginner issue.
 
         **Difficulty:**
 
@@ -113,7 +113,7 @@ body:
         > - Keeping your fork up to date with main by [rebasing](https://github.com/hiero-ledger/sdk-collaboration-hub/blob/main/guides/issue-progression/for-developers/rebasing.md)
         > - Looking things up on your own before asking for help
 
-        If any of that feels unfamiliar, good first issues might still be the most rewarding path for you right now — [find one here](https://github.com/issues?q=is%3Aopen%20is%3Aissue%20org%3Ahiero-ledger%20archived%3Afalse%20no%3Aassignee%20(label%3A%22good%20first%20issue%22%20OR%20label%3A%22skill%3A%20good%20first%20issue%22)%20(repo%3Ahiero-ledger%2Fhiero-sdk-cpp%20OR%20repo%3Ahiero-ledger%2Fhiero-sdk-swift%20OR%20repo%3Ahiero-ledger%2Fhiero-sdk-python%20OR%20repo%3Ahiero-ledger%2Fhiero-sdk-js%20OR%20repo%3Ahiero-ledger%2Fhiero-website)).
+        If any of that feels unfamiliar, Good First Issues might still be the most rewarding path for you right now — [find one here](https://github.com/issues?q=is%3Aopen%20is%3Aissue%20org%3Ahiero-ledger%20archived%3Afalse%20no%3Aassignee%20(label%3A%22good%20first%20issue%22%20OR%20label%3A%22skill%3A%20good%20first%20issue%22)%20(repo%3Ahiero-ledger%2Fhiero-sdk-cpp%20OR%20repo%3Ahiero-ledger%2Fhiero-sdk-swift%20OR%20repo%3Ahiero-ledger%2Fhiero-sdk-python%20OR%20repo%3Ahiero-ledger%2Fhiero-sdk-js%20OR%20repo%3Ahiero-ledger%2Fhiero-website)).
         You can always come back when you are ready.
 
         ### ⚠️ AI Usage Policy

.github/scripts/bot-gfi-assign-on-comment.js

@@ -60,7 +60,7 @@ function commentRequestsAssignment(body) {
 }
 
 /**
- * Returns true if the issue has the good first issue label.
+ * Returns true if the issue has the Good First Issue label.
  */
 function issueIsGoodFirstIssue(issue) {
     const labels = issue?.labels?.map(label => label.name) ?? [];

.github/scripts/bot-next-issue-recommendation.js

@@ -59,7 +59,7 @@ module.exports = async ({ github, context, core }) => {
     // Determine issue difficulty level
     const difficultyLevels = {
       beginner: labelSet.has('beginner'),
-      goodFirstIssue: labelSet.has('good first issue'),
+      goodFirstIssue: labelSet.has('Good First Issue'),
       intermediate: labelSet.has('intermediate'),
       advanced: labelSet.has('advanced'),
     };
@@ -85,7 +85,7 @@ module.exports = async ({ github, context, core }) => {
 
     if (recommendedIssues.length === 0) {
       isFallback = true;
-      recommendedIssues = await searchIssues(github, core, repoOwner, repoName, 'good first issue');
+      recommendedIssues = await searchIssues(github, core, repoOwner, repoName, 'Good First Issue');
       recommendedLabel = 'Good First Issue';
     }
 
@@ -170,7 +170,7 @@ async function generateAndPostComment(github, context, core, prNumber, recommend
       `org:${context.repo.owner}`,
       'archived:false',
       'no:assignee',
-      '(label:"good first issue" OR label:"skill: good first issue")',
+      '(label:"Good First Issue" OR label:"skill: Good First Issue")',
       `(${repoQuery})`,
     ].join(' ');
 

.github/workflows/bot-gfi-candidate-notification.yaml

@@ -14,7 +14,7 @@ permissions:
 jobs:
   gfi_candidate_notify_team:
     runs-on: hl-sdk-py-lin-md
-    if: contains(github.event.issue.labels.*.name, 'good first issue candidate')
+    if: contains(github.event.issue.labels.*.name, 'Good First Issue candidate')
     concurrency:
       group: gfi-candidate-${{ github.event.issue.number }}
       cancel-in-progress: false

docs/sdk_developers/training/workflow/04_assigning_issues.md

@@ -1,6 +1,6 @@
 ## Getting Assigned to an Issue
 
-Claim an issue as yours to work on by commenting on a good first issue with exactly: /assign
+Claim an issue as yours to work on by commenting on a Good First Issue with exactly: /assign
 
 We recommend Good First Issues for developers new to the Python SDK. These are easier and better documented tasks.