Delivery review changeset push failure

Chef Automate
1

What is actually happening here?

Chef Delivery
Loading configuration from /Users/matt/src/myproject
Review for change mybranch targeted for pipeline master
Created new patchset        
Failed to push branch to Bitbucket: fatal: remote error: Repository not found        
The requested repository does not exist, or you do not have permission to        
access it. 
(url)

The branch exists on both origin and delivery, I can manipulate them just fine with git. Which is failing to push? Not being able to put delivery into a debug output mode is rather frustrating.

The updated changeset does appear on the Chef Automate server despite whatever supposedly failing push.

2

I figured this out. It looks like that part is to create a pull request on the repo, which of course, the user account you setup in the Chef Automate console for the SCM config is who needs write permissions on the repo in order to do. Added Chef user to my repos with the write permission and, voila, it creates and links a new pull request.