Uh oh!
There was an error while loading. Please reload this page.
docs: clarify the security process in the triage role - #6217
Merged
Conversation
UlisesGascon
approved these changes
Dec 13, 2024
UlisesGascon
left a comment
Member
There was a problem hiding this comment.
LGTM! I think that this covers what we had discussed in our last meeting, also the triage team has limit rights to delete issues, so this is the best approach (IMO)
IamLizu
approved these changes
Dec 19, 2024
UlisesGascon
commented
Dec 20, 2024
Member
As this was already discussed in a TC Meeting and it is aligned with that discussion, I will merge the PR 👍 |
Closed
Merged
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for freeto join this conversation on GitHub.
Already have an account?
Sign in to comment
6 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
As discussed in the recent TC meeting, it is important to clarify what to do as a triager regarding security matters.
cc: @expressjs/express-tc @expressjs/triagers