You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Another behavior of @jekyllbot (that's relatively new), when an issue comes in and @mentions an affinity team, one of the team captains are randomly assigned the issue. They're obviously free to unassigned or change assignment, but it creates a sense of distributed ownership of issues, based on where they are in the codebase.
The text was updated successfully, but these errors were encountered:
After #13, here's how this could potentially be implemented using pre-built actions (which aren't implemented yet):
- on:
- issues.created
- pull_request.created
- issues.labeled
- pull_request.labeledwhen:
label: securitythen:
# Assign a specific personassign: benbalter# or: Assign a random maintainer with commit accessassign:
random: true# or: Assign a random person from a teamassign:
random:
from_team: security-first-responders# or: Assign a random person from a fileassign:
random:
from_file: .github/maintainers.yml
Another behavior of @jekyllbot (that's relatively new), when an issue comes in and @mentions an affinity team, one of the team captains are randomly assigned the issue. They're obviously free to unassigned or change assignment, but it creates a sense of distributed ownership of issues, based on where they are in the codebase.
The text was updated successfully, but these errors were encountered: