-
-
Notifications
You must be signed in to change notification settings - Fork 13
Open
Labels
acceptedThere is consensus among the team that this change meets the criteria for inclusionThere is consensus among the team that this change meets the criteria for inclusionenhancementNew feature or requestNew feature or request
Description
What problem do you want to solve?
Hello,
Currently, the code-explorer
repository does not have the add-to-triage
GitHub workflow, so issues and PRs are not moved to the triage board automatically.
So, I would like to suggest adding automation to this repository and to the repositories that do not have it yet.
But I have a question about this.
The markdown
repository has the add-to-triage
workflow, so it works, I guess.
However, the css
repository does not have the add-to-triage
workflow, but it still works. How is that possible?
I took a look at the eslint-github-bot
, but there was no workflow related to triage.
I would be happy to get an answer for this.
What do you think is the correct solution?
.
Participation
- I am willing to submit a pull request for this change.
Additional comments
No response
Metadata
Metadata
Assignees
Labels
acceptedThere is consensus among the team that this change meets the criteria for inclusionThere is consensus among the team that this change meets the criteria for inclusionenhancementNew feature or requestNew feature or request
Type
Projects
Status
Ready to Implement