Proposal: Link the contribution-kinds directive to the available calls in the github API, or perhaps an explicit subset of these calls.
Rationale: Bots are going to be automated agents (by definition), so what they can/cannot do to a repo will be determined by the github API. Instead of curating the specific contribution-kinds in the bots.yml spec, we could just allow this directive to take on any value that's available as a call in the github API (e.g., that causes visible mutation to a project's resources). This will also allow bots.yml evolve naturally with github.
One potential con is that API changes would require potential bots.yml file changes, or require bots to support backward compatibility. On the flip side, significant API changes are rare.
Proposal: Link the contribution-kinds directive to the available calls in the github API, or perhaps an explicit subset of these calls.
Rationale: Bots are going to be automated agents (by definition), so what they can/cannot do to a repo will be determined by the github API. Instead of curating the specific contribution-kinds in the bots.yml spec, we could just allow this directive to take on any value that's available as a call in the github API (e.g., that causes visible mutation to a project's resources). This will also allow bots.yml evolve naturally with github.
One potential con is that API changes would require potential bots.yml file changes, or require bots to support backward compatibility. On the flip side, significant API changes are rare.