Maintenance: introduce new need-response label that will trigger stale automation

[dreamorosi]

Summary

The repo has an automation that runs every night and checks for stale issues - issues that haven't been interacted with for 2 weeks - and closes them after they've been marked as stale for a week.

The automation works by looking at issue labels and update dates. This issue tracks the introduction of a new label dedicated specifically to this workflow.

Why is this needed?

When I configured the workflow I mistakenly overloaded the meaning of other existing labels (need-more-information first, then need-customer-feedback). This has caused the workflow to mistakenly close some issues that had been intentionally left open to either gather feedback or signal that more info is needed.

Which area does this relate to?

Automation

Solution

Introduce a new need-response label that is linked only to the Stale automation & update the MAINTAINERS.md document to reflect the change.

Acknowledgment

• This request meets Lambda Powertools Tenets
• Should this be considered in other Lambda Powertools languages? i.e. Python, Java, and .NET

Future readers

Please react with 👍 and your use case to help us understand customer demand.

[github-actions]

⚠️ COMMENT VISIBILITY WARNING ⚠️

Comments on closed issues are hard for our team to see.
If you need more assistance, please either tag a team member or open a new issue that references this one.
If you wish to keep having a conversation with other community members under this issue feel free to do so.