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

hh: thoughts on consequences of updating team names #51

Open
cirocosta opened this issue May 21, 2019 · 0 comments
Open

hh: thoughts on consequences of updating team names #51

cirocosta opened this issue May 21, 2019 · 0 comments

Comments

@cirocosta
Copy link
Member

We just recently saw how frustrating it is for a team to have their team name changes and then forgetting to change the name used in team authorized keys.

It seems to me that there are two ways that we could solve this:

  • leaving only ourselves as owners and centralizing the set-team like we used to do, or
  • having a checklist for those who get to perform operations like renaming teams for other teams.

Thoughts?

Thanks!

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