chore: rename templates for clarity (#1265)

[parvninama]

This pull request renames several Github templates in the repository to improve clarity and maintain consistency.

• Updated template filenames and references to make their purpose more obvious.
• No functional changes or code logic modifications were made.
• Ensures that future contributions are easier to navigate and understand.

Closes #1265

[github-actions]

Hi, this is MergeConflictBot.
Your pull request cannot be merged because it contains merge conflicts.

Please resolve these conflicts locally and push the changes.

To assist you, please read:

• Resolving Merge Conflicts
• Rebasing Guide

Thank you for contributing!

[coderabbitai]

📝 Walkthrough

Walkthrough

The pull request updates the CHANGELOG.md file with an entry documenting the renaming of GitHub issue templates for improved clarity. The underlying template files have been renamed as referenced in the changelog entry.

Changes

Cohort / File(s)	Summary
Changelog Entry CHANGELOG.md	Added entry under Unreleased > Changed: "Renamed templates for improved clarity (#1265)"

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~3 minutes

Pre-merge checks

❌ Failed checks (1 inconclusive)

Check name	Status	Explanation	Resolution
Linked Issues check	❓ Inconclusive	The PR provides a changelog entry and addresses the core requirement to rename templates, but the raw_summary only shows CHANGELOG.md changes without confirming the actual template file renames were completed.	Verify that the template files in .github/ISSUE_TEMPLATE were actually renamed as specified in issue #1265 (04_good_first_issue_candidate.yml → 01_good_first_issue_candidate.yml and 01_good_first_issue.yml → 04_good_first_issue.yml).

✅ Passed checks (4 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title accurately summarizes the main change - renaming templates for clarity - and is directly related to the changeset.
Description check	✅ Passed	The description is relevant to the changeset, explaining template renames for improved clarity and consistency with no functional changes.
Out of Scope Changes check	✅ Passed	The raw_summary indicates only CHANGELOG.md was modified with no other functional changes, suggesting changes are within scope.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

---

📜 Recent review details

Configuration used: Path: .coderabbit.yaml

Review profile: ASSERTIVE

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between e53acb1 and e3195cf.

📒 Files selected for processing (3)

• .github/ISSUE_TEMPLATE/01_good_first_issue_candidate.yml
• .github/ISSUE_TEMPLATE/04_good_first_issue.yml
• CHANGELOG.md

🔇 Additional comments (2)

CHANGELOG.md (2)

80-80: Verify that all template files and references were renamed.

The changelog entry documents the template renaming, but GitHub's template order depends on filename ordering. Ensure that:

1. .github/ISSUE_TEMPLATE/04_good_first_issue_candidate.yml → .github/ISSUE_TEMPLATE/01_good_first_issue_candidate.yml
2. .github/ISSUE_TEMPLATE/01_good_first_issue.yml → .github/ISSUE_TEMPLATE/04_good_first_issue.yml
3. Any references to old filenames in config.yml, documentation, or other code are updated
4. No references to the old filenames remain in the codebase

---

80-80: Inconsistent issue reference formatting.

The reference format [(#1265)] uses square brackets with parentheses, which is inconsistent with the rest of the changelog. Other entries use either (#XXXX) (lines 81, 83, 85) or [#XXXX](URL) (line 84).

🔎 Proposed fix

-- Renamed templates for improved clarity [(#1265)]
+- Renamed templates for improved clarity (#1265)

Likely an incorrect or invalid review comment.

Warning

Review ran into problems

🔥 Problems

Git: Failed to clone repository. Please run the @coderabbitai full review command to re-trigger a full review. If the issue persists, set path_filters to include or exclude specific files.

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[parvninama]

Thanks for the opportunity!
All checks are now passing — happy to address any feedback.

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.

@@           Coverage Diff           @@
##             main    #1297   +/-   ##
=======================================
  Coverage   91.80%   91.80%           
=======================================
  Files         139      139           
  Lines        8484     8484           
=======================================
  Hits         7789     7789           
  Misses        695      695           

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

[exploreriii]

This is a really valuable contribution, many thanks! we have been looking for help on this for a while :D

[parvninama]

Thank you! I’m glad I could help .