nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Pull request from command line: reviewers by other than UUID

Oliver Schoenborn

I am able to create a pull request from command line, the only thing I find painful is the reviewers are specified by UUID, I can see why that is safest but is there another way? Right now:

"reviewers": [
    {
"uuid": "{4ebe61bf-...-a368a41c78f6}"
    },
    {
"uuid": "{2ce53e84-...-fff39d658b49}"
    }
]

This is not very user-friendly, and I can't even put comments to indicate who those people are at least for whoever reads the PR.json that contains the above.

Accepted answers

Oliver Schoenborn

For 2.0 API:

In my case the main reason I use CLI is because I have a bunch of identical PR's to make on dozen repos, so the way I handle this now is I create one PR programmatically, use the CLI to get the PR, pare down the JSON so only title, description, reviewers, and source remain, and POST the file to as many repos as I need.

All comments

thinksabin

in rest api 1.0, we can use username in the api call.

Oliver Schoenborn

thanks, good to know (unfortunately I'm using 2.0)

Oliver Schoenborn

For 2.0 API:

Daniil Penkin

Hello @Oliver Schoenborn,

In the payload you send to the API endpoints you actually can refer to users using their usernames — you obviously need to know them in advance.

"reviewers": [
    {
        "username": "<username>"
    }
]

In the API responses, however, usernames are not returned anymore due to requirements introduced by GDPR.

Note that a user might change their username at any time, and this will break a request with the payload mentioned above. Unlike username, UUID and Atlassian ID (uuid and account_id in JSON, respectively) would remain same in that case.

Hope this helps.

Cheers,
Daniil

Daniil Penkin

Hi @thinksabin,

Just a heads up that REST API 1.0 has been deprecated around a year ago and currently is in a phase of gradual termination. So the endpoints you might still be able to use now will likely stop working in the future. Please consider migrating to API 2.0.

Let me know if you have any questions.

Cheers,
Daniil

thinksabin

hi @Daniil Penkin ,

thanks for the heads up, I was unaware about the termination of the api 1.0. Thanks i will try to modify my automation script.

Oliver Schoenborn_ajxctr

Thanks Daniil I tried username and got bad request error. I can use username if I also include uuid. Which is useful to document who the uuid is, but I still have to know the uuid.

Daniil Penkin

Hm, did you get any error description in the response payload?

I'm able to create a PR using API with reviewers resolved by username:

❯ curl -X POST -H "Content-Type: application/json" -u detouched:pEPcSZYDpP4SmgDMbkL9 "https://api.bitbucket.org/2.0/repositories/detouched/docker-spb/pullrequests" -d '{
  "title": "Test Pull Request",
  "source": {
    "branch": {
      "name": "1.3.8"
    }
  },
  "destination": {
    "branch": {
      "name": "master"
    }
  },
  "reviewers": [
    {
      "username": "dpenkin"
    }
  ]
}'

I get 201 back and PR object JSON.

So I'm wondering maybe you get bad request because of some other problem?

Cheers,
Daniil

Oliver Schoenborn_ajxctr

No info beyond bad request. Likely because username invalid. I went to the user's page and could see the uuid in the link and their name on the page so I used that but that's probably their display name (and I tried with display_name instead of uuid or username but also got bad request). How can I find a user's username?

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

cloud

bitbucket

bitbucket-cloud