Add rule to mark Bearer token issues as security issues #32709
Conversation
quarkus-bot
bot
added
the
area/infra-automation
.github/quarkus-github-bot.yml
Outdated
| @@ -226,6 +226,10 @@ triage: | |||
| - extensions/security/ | |||
| - extensions/elytron | |||
| - integration-tests/elytron | |||
| - id: bearer-token | |||
| labels: [area/security] | |||
| title: "Bearer token" | |||
There was a problem hiding this comment.
I did a quick search and I think we should go with the following. It won't catch too many false positives AFAICS.
| title: "Bearer token" | |
| title: "bearer" |
There was a problem hiding this comment.
I am not sure it's correct, so I'll leave it to @sberyozkin to break the tie
There was a problem hiding this comment.
FWIW, here's what I did: https://github.com/quarkusio/quarkus/issues?q=is%3Aissue+bearer+in%3Atitle+
But I don't mind either way, feel free to merge if you have a strong opinion about it.
There was a problem hiding this comment.
Yeah you are right, it does look good indeed. Let's get @sberyozkin blessing first and then I'll change it.
There was a problem hiding this comment.
I changed this, do you agree @sberyozkin ?
There was a problem hiding this comment.
Cool, PR should be ready then
Done because quarkusio#32701 was left as `needs-triage`
geoand
force-pushed
the
bearer-token-notify
branch
from
c30d072 to
869c248
Compare
|
💪🏼 |
Done because #32701 was left as
needs-triage