Harness Git Experience permissions inherited from GitHub
T
Turquoise Loon
As commented in several meetings with Harness. We currently have a problem with the way Harness uses the connectors when making changes to Git Experience resources.
The permissions that users have in GitHub avoid the commit directly to main branches, making mandatory the use of Pull Requests to commit changes to the default branch. However, the connector configured in Harness uses a GitHub App with permissions to commit to main branches (necessary for Git Experience).
That is making possible that an user who changes resources from Harness UI can commit those changes directly to the main branch. In GitHub it appears like the user is pushing the commit, but the Harness impersonates as the user doing the change and pushes the change with its credentials (see attached).
This request is to add the feature to use the permissions from GitHub when doing changes from Harness, instead of using the connector.
Log In