-
Notifications
You must be signed in to change notification settings - Fork 124
Ability to customize team name #12
Comments
this is already supported. See the bottom of https://lgtm.co/docs/maintainers/ |
Oh cool! Thanks @bradrydzewski! Sadly it looks like I can only have 1 team named |
we have a placeholder in the right now the team name is hard-coded: if the above functions are altered to pass the team name we could source the team name from the -members, merr := cache.GetMembers(c, user, repo.Owner)
+members, merr := cache.GetMembers(c, user, repo.Owner, rcfile.Team) please note that I'm not actively working on feature requests. Lgtm meets my specific needs and I have to dedicate my time to drone/drone so any new features or enhancements will need to come from the community via pull request |
Great, thanks @bradrydzewski. I'll put some time into making a PR some point this week. |
+1 Is this being completed or could it use some help? |
@bradynpoulsen help wanted :) |
@bradrydzewski Has this format been adopted? #49 (comment) I'm not too familiar with the organization of the project, where do I find and example at getting values from the config (or the default if not configured)? |
Here is a pull request that is working on this #50 |
It can be a pain for teams with high turnover, or teams with lots of repositories, to maintain the
MAINTAINERS
file. Github and Bitbucket provide "teams" which allow project maintainers to set repository permissions - these teams could be used as a way to determine the maintainers of the code.As an example, the ChaiJS project (https://github.com/chaijs) has a team for every repository (https://github.com/orgs/chaijs/teams) - if these could be used as a standin for maintaining a
MAINTAINERS
file this would ease the burden of working with LGTM.The text was updated successfully, but these errors were encountered: