Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Allow automation to communicate person responsible for it (CODEOWNERS) #11

Open
patcon opened this issue Apr 10, 2019 · 0 comments
Open

Comments

@patcon
Copy link
Member

patcon commented Apr 10, 2019

In this evolving philosophy of community automation, I'm leaning toward:

  1. Be clear about a point of contact for support. Don't assume people know to check Git commit history on code.

Right now, there's a convention of informally pointing out the code for the automation in each automated message in Slack. If someone is technically inclined, they can explore the code repo and see who wrote the code, but that's perhaps not obvious.

So the idea is to add parsing of the CODEOWNER file on GitHub, and use that (an email for starters) to resolve to a Slack username. Then, the templates and helpers for automated messages can make it simple to refer to the person responsible for the automation :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant