Update new-feature.yml

[Krishanx92]

Purpose

Explain why this feature or fix is required. Describe the underlying problems, issues, or needs driving this feature/fix and include links to related issues in the following format: Resolves issue1, issue2, etc.

Goals

Describe what solutions this feature or fix introduces to address the problems outlined above.

Approach

Describe how you are implementing the solutions. Include an animated GIF or screenshot if the change affects the UI. Include a link to a Markdown file or Google doc if the feature write-up is too long to paste here.

User stories

Summary of user stories addressed by this change>

Documentation

Link(s) to product documentation that addresses the changes of this PR. If no doc impact, enter “N/A” plus brief explanation of why there’s no doc impact

Automation tests

• Unit tests

  Code coverage information

• Integration tests

  Details about the test cases and coverage

Security checks

• Followed secure coding standards in http://wso2.com/technical-reports/wso2-secure-engineering-guidelines? yes/no
• Ran FindSecurityBugs plugin and verified report? yes/no
• Confirmed that this PR doesn't commit any keys, passwords, tokens, usernames, or other secrets? yes/no

Samples

Provide high-level details about the samples related to this feature

Related PRs

List any other related PRs

Test environment

List all JDK versions, operating systems, databases, and browser/versions on which this feature/fix was tested

[coderabbitai]

Warning

Review limit reached

@Krishanx92, you've reached your PR review limit, so we couldn't start this review.

Next review available in: 53 minutes

Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available.
You're only billed for reviews past your plan's rate limits ($0.25/file).

How can I continue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews.

How do review limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability.

For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window.

Please refer docs for additional details.

Review details

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro

Run ID: 1411b3e8-6e30-4acf-bb79-4dee18e8b7b2

📥 Commits

Reviewing files that changed from the base of the PR and between 916d3fa and 3f3fcc1.

📒 Files selected for processing (1)

• .github/ISSUE_TEMPLATE/new-feature.yml

📝 Walkthrough

Walkthrough

This PR updates checklist item text in the GitHub issue template for new features, renaming "Testing" to "Testing Complete" and "Documentation" to "Documentation Review" (with a typo "reviewd").

Changes

Issue Template Checklist Update

Layer / File(s)	Summary
Feature completion checklist wording .github/ISSUE_TEMPLATE/new-feature.yml	Checklist item labels renamed to "Testing Complete" and "Documentation Review" (with typo "reviewd").

Estimated code review effort: 1 (Trivial) | ~2 minutes

Possibly related PRs

• wso2/api-platform#2481: Both PRs modify the same .github/ISSUE_TEMPLATE/new-feature.yml checklist items.

Suggested reviewers: RakhithaRR, Tharsanan1, chamilaadhi, AnuGayan, ashera96

🚥 Pre-merge checks | ✅ 4 | ❌ 1

❌ Failed checks (1 warning)

Check name	Status	Explanation	Resolution
Description check	⚠️ Warning	The description is only the untouched template and lacks filled-in purpose, goals, approach, tests, and other required details.	Replace the template text with concrete details for each required section, including purpose, goals, approach, tests, security checks, and environment.

✅ Passed checks (4 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title accurately reflects the only substantive change: updates to new-feature.yml.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch Krishanx92-patch-3

---

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.}

[coderabbitai]

Actionable comments posted: 1

🤖 Prompt for all review comments with AI agents

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

Inline comments:
In @.github/ISSUE_TEMPLATE/new-feature.yml:
- Line 64: The checklist label in the new-feature issue template contains a typo
and awkward trailing phrasing; update the Documentation Review label text in the
template so it reads cleanly and correctly, fixing the misspelling of “reviewd”
and removing the incomplete “and need to reviewd” clause while keeping the
intended meaning intact.

🪄 Autofix (Beta)

Fix all unresolved CodeRabbit comments on this PR:

• Push a commit to this branch (recommended)
• Create a new PR with the fixes

---

ℹ️ Review info

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro

Run ID: 0acc402e-43fc-4fdc-959d-58e1deb75b0a

📥 Commits

Reviewing files that changed from the base of the PR and between 539468c and 916d3fa.

📒 Files selected for processing (1)

• .github/ISSUE_TEMPLATE/new-feature.yml