Skip to content
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

PackageRules: add DepNamePrefix matcher #27048

Closed
secustor opened this issue Feb 4, 2024 · 2 comments · Fixed by #28542
Closed

PackageRules: add DepNamePrefix matcher #27048

secustor opened this issue Feb 4, 2024 · 2 comments · Fixed by #28542
Assignees
Labels
core:package-rules Relating to package-rules e.g. matchers good first issue Suitable for new contributors priority-3-medium Default priority, "should be done" but isn't prioritised ahead of others type:feature Feature (new functionality)

Comments

@secustor
Copy link
Collaborator

secustor commented Feb 4, 2024

We currently have an PackageNamePrefix matcher, but we currently do not have equivalent for depNames.

Other matchers for depName:

@secustor secustor added type:feature Feature (new functionality) priority-3-medium Default priority, "should be done" but isn't prioritised ahead of others core:package-rules Relating to package-rules e.g. matchers labels Feb 4, 2024
@secustor secustor added the good first issue Suitable for new contributors label Feb 5, 2024
@yinm
Copy link
Contributor

yinm commented Apr 13, 2024

Can I try it?

@secustor
Copy link
Collaborator Author

Sure thing!

@github-actions github-actions bot locked as resolved and limited conversation to collaborators May 21, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
core:package-rules Relating to package-rules e.g. matchers good first issue Suitable for new contributors priority-3-medium Default priority, "should be done" but isn't prioritised ahead of others type:feature Feature (new functionality)
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants
@yinm @secustor and others