Why is Source Control read only for delegated developers?

[Craig22]

I've assigned the Source Control permission (via Manage Collaborators) to a scoped app for my delegated developers and they get the Source Control link show up but can't interact with it in any way.

Is there something else I need to do to enable them to do stuff with Source Control?

[WORKFLOW-COWBOY]

Is it possible for you to set up the Credentials and Source Control for the Developers and then they can manage their own commits, branching, etc. after that? 

It might be possible to make a Catalog Item and Flow to set it up for them. 

[JC15]

OK, I think this is a bug which needs to be fixed.

But as a work-around, you can make an ACL like this, if you are willing to give them access to the Github credential. 

[JC15]

Just got an update to this 6 month old ticket... Being told it was worked PRB1775349

Per SNOW support: 

To resolve this, add a system property 'glide.source_control.default_basic_auth_credential_sys_id' in the sys_properties table and its value will be the sys_id of the credentials (which has been given to link the app to the source control) record. The sys_id of the credentials can be obtained from the table 'discovery_credentials_list'.

This will be the same credential record on the corresponding sys_repo_config record for this application.

1. Go to the table 'discovery_credentials'
2. Locate the record for the Application
3. Get the sys_id
4. Open the table 'sys_properties'
5. Create a new record:
   • Name: 'glide.source_control.default_basic_auth_credential_sys_id'
   • Type: 'String'
   • Value: <sys_id> taken at step 3