-
Notifications
You must be signed in to change notification settings - Fork 1k
Implement initial rollout of PEP 715 #14017
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
Conversation
This test isn't passing yet.
if someone has a direct Role and a TeamRole we don't want to bother them twice
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
🎉
Co-authored-by: William Woodruff <[email protected]>
contributors += project.organization.owners | ||
for teamrole in project.team_project_roles: | ||
contributors += teamrole.team.members | ||
|
||
for contributor in sorted(set(contributors)): |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
thought: I've seen this kind of pattern a couple of times now, so we likely want to queue up a feature request for Project.all_members
or such that figures this out.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I agree, I think Project.contributors
would fit nicely since thats how it is used most frequently.
Also an update to User.projects
would be a step towards #13840
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'd suggest both of those are addressed in a separate PR. (This use case is temporary).
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Of course! I use Conventional Comments for code reviews.
No description provided.