something wrong with gitlab ProjectAccess

[fangweisi]

I found that pipeline use "Permissions.ProjectAccess.AccessLevel" to deside if I can pull the code.
So I must add the right to project not to the group.
I used to make my account as the owner of the group, but it's not work in rancher, it show "no permission".
After I make the account as the master of the project, it works.

[gitlawr]

Actually, it detects admin permission for hooks using both ProjectAccess and GroupAccess.
Per Gitlab's repo API, a user can still have permissions even though these two fields are null.
The issue probably happens when a user's project is shared with a group. The shared_with_groups field does not tell the real permission of the current user unless user-group relations are inspected.

//info from repo api
"shared_with_groups": [
            {
                "group_id": 2, 
                "group_name": "mygroup", 
                "group_access_level": 40
            }
        ], 
"permissions": {
            "project_access": null, 
            "group_access": null
        }

As workarounds, add the user to be a member or transfer the project to the group should help.