-
-
Notifications
You must be signed in to change notification settings - Fork 5
Suggestion: Project triaging automation #5
Copy link
Copy link
Closed
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
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
Complete
What problem do you want to solve?
Hello,
Currently, the
code-explorerrepository does not have theadd-to-triageGitHub 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
markdownrepository has theadd-to-triageworkflow, so it works, I guess.However, the
cssrepository does not have theadd-to-triageworkflow, 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
Additional comments
No response