Skip to content
This repository has been archived by the owner on May 16, 2022. It is now read-only.

A member of 'a team' can't create release issue #150

Open
jpopelka opened this issue Feb 18, 2019 · 5 comments
Open

A member of 'a team' can't create release issue #150

jpopelka opened this issue Feb 18, 2019 · 5 comments
Labels
bug Something isn't working

Comments

@jpopelka
Copy link
Member

jpopelka commented Feb 18, 2019

For example in packit/ogr#15 @lachmanfrantisek was ignored because

WARNING Author association 'CONTRIBUTOR' not in ['MEMBER', 'OWNER', 'COLLABORATOR']

even he was in part of 'The packit team' whose members should be admins in the ogr project.

Once we added him as collaborator, the issue was processed.

FYI: https://github.com/CoolProp/CoolProp/wiki/Contributors-vs-Collaborators

@TomasTomecek
Copy link
Member

github roles are very clear and easy to use... FML

@jpopelka
Copy link
Member Author

Ok, so I'm confused now since my user-cont/conu#353 was processed even I'm not explicitly added as collaborator in https://github.com/user-cont/conu/settings/collaboration

@TomasTomecek
Copy link
Member

could it be just a race condition that github did not update the roles in their system in time and their API returned outdated info?

@jpopelka
Copy link
Member Author

I don't think so, the 'The packit team' was added some time ago and also Franta has been a member for some time.

@TomasTomecek
Copy link
Member

oki, we should investigate and resolve this then

@TomasTomecek TomasTomecek added the bug Something isn't working label Mar 4, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants