Add IAM CTL tool checklist item to task issue template

[RovinKYK]

Adds a checklist item to the task issue template to prompt contributors to consider whether their change affects the IAM CTL tool and whether the necessary changes have been made in it.

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: 8b98998c-caaa-47cd-bdfe-7b9842b8cf3e

📥 Commits

Reviewing files that changed from the base of the PR and between 56d94d5 and 363c6cc.

📒 Files selected for processing (4)

• .github/ISSUE_TEMPLATE/bug.yml
• .github/ISSUE_TEMPLATE/improvement.yml
• .github/ISSUE_TEMPLATE/new-feature.yml
• .github/ISSUE_TEMPLATE/task.yml

✅ Files skipped from review due to trivial changes (2)

• .github/ISSUE_TEMPLATE/improvement.yml
• .github/ISSUE_TEMPLATE/bug.yml

🚧 Files skipped from review as they are similar to previous changes (1)

• .github/ISSUE_TEMPLATE/task.yml

---

📝 Walkthrough

Summary

This PR adds IAM CTL (Identity Access Management Command-Line Tool) awareness to the repository's GitHub issue templates by inserting two checklist items into the "Developer Checklist" of the main templates:

1. A prompt asking whether the change affects IAM CTL behavior.
2. A confirmation that any necessary updates to the IAM CTL tool have been made.

Changes

Added the two IAM CTL checklist items to these templates:

• .github/ISSUE_TEMPLATE/task.yml
• .github/ISSUE_TEMPLATE/bug.yml
• .github/ISSUE_TEMPLATE/improvement.yml
• .github/ISSUE_TEMPLATE/new-feature.yml

Each template received two new checklist lines to remind contributors to consider and document IAM CTL impact when filing issues.

Walkthrough

Four GitHub issue templates (task, bug, improvement, new-feature) were updated to add two Developer Checklist items: a checkbox asking whether the change affects IAM CTL behavior and a follow-up checkbox confirming that any required IAM CTL tool updates have been performed.

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title accurately describes the main change: adding IAM CTL tool checklist items to issue templates, though it only mentions the task template while the changeset includes updates to four templates.
Description check	✅ Passed	The description is directly related to the changeset, explaining the purpose of adding IAM CTL tool checklist prompts, though it specifically references only the task template while the PR modifies four templates.
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.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests

---

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

[Copilot]

Pull request overview

Note

Copilot was unable to run its full agentic suite in this review.

Adds an additional checklist section to the Task issue template to prompt contributors to consider impacts/updates needed in the IAM CTL tool.

Changes:

• Added a new “[IAM CTL] …” checklist question to the Task issue template.
• Added a follow-up checkbox to confirm required IAM CTL tool changes were made.

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud