Merged
Conversation
lumirlumir
commented
Aug 3, 2025
Member
Yes.
Yes. |
nzakas
approved these changes
Aug 4, 2025
Member
nzakas
left a comment
There was a problem hiding this comment.
LGTM. Leaving open for @lumirlumir to decide if it's ready for merge based on my comment.
lumirlumir
commented
Aug 5, 2025
Member
Author
lumirlumir
left a comment
There was a problem hiding this comment.
Thanks for checking! Everything looks good, so I'll go ahead and merge it. 👍
This was referenced Aug 5, 2025
This was referenced Aug 5, 2025
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 free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 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.
Prerequisites checklist
What is the purpose of this pull request?
Hi,
In this PR, I've created the
add-to-triage.ymlworkflow. (You can find the guides for the reusable workflow here.)FYI, This workflow is also triggered in this repository, as I used the
on.issuesandon.pull_requestevents.Other repositories can use this workflow as well, since I included the
workflow_callevent.I've tested this workflow in my personal repository, and it works as expected except for the part where a token is required.
It means that the workflow is triggered when issues and pull requests are opened, reopened, or transferred.
What changes did you make? (Give an overview)
add-to-triage.ymlworkflow..gitignore.editorconfigfile, referring to https://github.com/eslint/markdown/blob/main/.editorconfig.Related Issues
Ref: #4, #5
Is there anything you'd like reviewers to focus on?
There are a few prerequisites for this workflow to function as expected:
PROJECT_BOT_TOKENsecret set at the organization level?Needs Triagecolumn set as the default for the "Triage" project board?It would be great if these items could be addressed before wrapping up this work!