CI/CD: Optional Role-Based First-Claim Assignment Automation

[aniket866]

Feature and its Use Cases

Overview

This proposal suggests introducing an optional Role-Based First-Claim Auto Assignment system at the Template Repository level.

The purpose of this feature is to streamline issue assignment when issues are created by authorized roles, while still preserving maintainer flexibility and control.

Problem Statement

When an issue is raised by a Maintainer, Knight, or Member, contributors often start requesting assignment in the comments.

Currently, maintainers need to:

• Monitor requests manually
• Decide who should be assigned
• Manage queue fairness

This can become time-consuming, especially in active repositories.

Proposed Solution

Introduce an optional automation system where:

• If an issue is created by an authorized role (Maintainer/Knight/Member)
• The first contributor who requests the issue is automatically assigned

This would follow a first-come-first-serve model.

Important Consideration (Why It Must Be Optional)

This feature should remain optional because maintainers may prefer to:

• Review different proposed approaches
• Evaluate technical understanding
• Ensure alignment with project architecture and long-term goals
• Assign the issue based on solution quality rather than queue order

In many cases, the best-aligned solution is more important than strict request timing. Therefore, maintainers must retain full flexibility to override or disable this automation.

Template-Level Configuration

This feature should be implemented in the Template Repository with configurable controls, such as:

• Repository variables (e.g., ENABLE_ROLE_BASED_ASSIGNMENT = true/false)
• Conditional workflow execution
• Feature flags

This ensures:

• Organization-wide scalability
• No forced behavior
• Per-repository control
• Long-term maintainability

Conclusion

This proposal aims to improve assignment efficiency while preserving maintainer authority.

By making the system optional at the template level, repositories can adopt structured automation without losing decision-making flexibility.

Feedback and direction on implementation are welcome.

Additional Context

@kpj2006 What's your view on this?,
feel free to assign

Code of Conduct

• I have joined the Discord server and will post updates there
• I have searched existing issues to avoid duplicates