Skip to content

[CI] Make issue labeler more robust #145431

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 1 commit into
base: main
Choose a base branch
from
Open

Conversation

snprajwal
Copy link
Contributor

The issue labeler handles commit access requests in a case-sensitive manner. This patch expands that to be case-insensitive.

The issue labeler handles commit access requests in a case-sensitive manner. This patch expands that to be case-insensitive.
@tbaederr tbaederr requested a review from tstellar June 24, 2025 03:57
@tstellar
Copy link
Collaborator

The regex is designed to match the summary that is automatically filled in for users when they click on the link in the developer guide. I only want users to apply by clicking the link and I don't want to match anything else.

@snprajwal
Copy link
Contributor Author

I understand the reasoning - it's just that there might be cases where someone goes through the link, discards the issue, and files it later (e.g. waiting for a PR to be merged before submitting the request). I personally found it easier to just type the issue title out instead of navigating the Developer Policy and clicking again, hence the change to retain the same regex but case-insensitive. We can also close this if you are sure you do not want the labeler to handle manually typed requests.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants