Bradley Herrup
09/22/2025, 4:50 PMAsk Inkeep
09/22/2025, 4:50 PMAsk Inkeep
09/22/2025, 4:50 PMpermit/generated/<env_id>
2. Once you've confirmed the branches exist, activate the repository using this API call :
curl -X PUT "<https://api.permit.io/v2/projects/<your-project-id-or-key>/repos/<your-repo-id-or-key>/activate>" -H "Authorization: Bearer <your-permit-api-key>"
The repository will remain in "pending" status until you run this activation command . This two-step process (create then activate) ensures your repository is properly configured before Permit starts syncing policies to it.
While the guide focuses on GitHub, it notes that the same steps apply to GitLab with minor modifications . Make sure you've:
⢠Added the SSH deploy key with write access to your GitLab repository
⢠Configured the SSH credentials correctly in your JSON payloadAsk Inkeep
09/22/2025, 4:51 PMBradley Herrup
09/22/2025, 4:51 PMBradley Herrup
09/22/2025, 4:53 PMThomas
09/22/2025, 5:09 PMGET on the repo API with the repo_id what do you get?Bradley Herrup
09/22/2025, 5:21 PMBradley Herrup
09/22/2025, 5:26 PMBradley Herrup
09/22/2025, 5:28 PMBradley Herrup
09/22/2025, 5:28 PMThomas
09/22/2025, 5:39 PMBradley Herrup
09/22/2025, 6:44 PMpermit support automation2
09/22/2025, 6:44 PMBradley Herrup
09/22/2025, 6:45 PMBradley Herrup
09/22/2025, 6:46 PMThomas
09/22/2025, 7:01 PMBradley Herrup
09/22/2025, 7:37 PMpermit support automation2
09/22/2025, 7:37 PMThomas
09/22/2025, 8:12 PM