-
-
Notifications
You must be signed in to change notification settings - Fork 3
/
openapi.yml
21837 lines (21231 loc) · 718 KB
/
openapi.yml
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
357
358
359
360
361
362
363
364
365
366
367
368
369
370
371
372
373
374
375
376
377
378
379
380
381
382
383
384
385
386
387
388
389
390
391
392
393
394
395
396
397
398
399
400
401
402
403
404
405
406
407
408
409
410
411
412
413
414
415
416
417
418
419
420
421
422
423
424
425
426
427
428
429
430
431
432
433
434
435
436
437
438
439
440
441
442
443
444
445
446
447
448
449
450
451
452
453
454
455
456
457
458
459
460
461
462
463
464
465
466
467
468
469
470
471
472
473
474
475
476
477
478
479
480
481
482
483
484
485
486
487
488
489
490
491
492
493
494
495
496
497
498
499
500
501
502
503
504
505
506
507
508
509
510
511
512
513
514
515
516
517
518
519
520
521
522
523
524
525
526
527
528
529
530
531
532
533
534
535
536
537
538
539
540
541
542
543
544
545
546
547
548
549
550
551
552
553
554
555
556
557
558
559
560
561
562
563
564
565
566
567
568
569
570
571
572
573
574
575
576
577
578
579
580
581
582
583
584
585
586
587
588
589
590
591
592
593
594
595
596
597
598
599
600
601
602
603
604
605
606
607
608
609
610
611
612
613
614
615
616
617
618
619
620
621
622
623
624
625
626
627
628
629
630
631
632
633
634
635
636
637
638
639
640
641
642
643
644
645
646
647
648
649
650
651
652
653
654
655
656
657
658
659
660
661
662
663
664
665
666
667
668
669
670
671
672
673
674
675
676
677
678
679
680
681
682
683
684
685
686
687
688
689
690
691
692
693
694
695
696
697
698
699
700
701
702
703
704
705
706
707
708
709
710
711
712
713
714
715
716
717
718
719
720
721
722
723
724
725
726
727
728
729
730
731
732
733
734
735
736
737
738
739
740
741
742
743
744
745
746
747
748
749
750
751
752
753
754
755
756
757
758
759
760
761
762
763
764
765
766
767
768
769
770
771
772
773
774
775
776
777
778
779
780
781
782
783
784
785
786
787
788
789
790
791
792
793
794
795
796
797
798
799
800
801
802
803
804
805
806
807
808
809
810
811
812
813
814
815
816
817
818
819
820
821
822
823
824
825
826
827
828
829
830
831
832
833
834
835
836
837
838
839
840
841
842
843
844
845
846
847
848
849
850
851
852
853
854
855
856
857
858
859
860
861
862
863
864
865
866
867
868
869
870
871
872
873
874
875
876
877
878
879
880
881
882
883
884
885
886
887
888
889
890
891
892
893
894
895
896
897
898
899
900
901
902
903
904
905
906
907
908
909
910
911
912
913
914
915
916
917
918
919
920
921
922
923
924
925
926
927
928
929
930
931
932
933
934
935
936
937
938
939
940
941
942
943
944
945
946
947
948
949
950
951
952
953
954
955
956
957
958
959
960
961
962
963
964
965
966
967
968
969
970
971
972
973
974
975
976
977
978
979
980
981
982
983
984
985
986
987
988
989
990
991
992
993
994
995
996
997
998
999
1000
openapi: 3.0.1
info:
contact:
email: [email protected]
name: Bitbucket Support
url: https://support.atlassian.com/bitbucket-cloud/
description: Code against the Bitbucket API to automate simple tasks, embed Bitbucket
data into your own site, build mobile or desktop apps, or even add custom UI add-ons
into Bitbucket itself using the Connect framework.
termsOfService: https://www.atlassian.com/legal/customer-agreement
title: Bitbucket API
version: "2.0"
servers:
- url: https://api.bitbucket.org/2.0
tags:
- description: ""
name: users
- description: ""
name: teams
- description: ""
name: repositories
- description: |-
Browse the source code in the repository and
create new commits by uploading.
name: source
- description: ""
name: refs
- description: ""
name: commits
- description: ""
name: pullrequests
- description: |-
The issue resources provide functionality for getting information on
issues in an issue tracker, creating new issues, updating them and deleting
them.
You can access public issues without authentication, but you can't gain access
to private repositories' issues. By authenticating, you will get the ability
to create issues, as well as access to updating data or deleting issues you
have access to.
name: issue_tracker
- description: ""
name: wiki
- description: ""
name: downloads
- description: ""
name: snippets
- description: |
Webhooks provide a way to configure Bitbucket Cloud to make requests to
your server (or another external service) whenever certain events occur in
Bitbucket Cloud.
A webhook consists of:
* A subject -- The resource that generates the events. Currently, this resource
is the repository, user account, or team where you create the webhook.
* One or more event -- The default event is a repository push, but you can
select multiple events that can trigger the webhook.
* A URL -- The endpoint where you want Bitbucket to send the event payloads
when a matching event happens.
There are two parts to getting a webhook to work: creating the webhook and
triggering the webhook. After you create a webhook for an event, every time
that event occurs, Bitbucket sends a payload request that describes the event
to the specified URL. Thus, you can think of webhooks as a kind of
notification system.
Use webhooks to integrate applications with Bitbucket Cloud. The following
use cases provides examples of when you would want to use webhooks:
* Every time a user pushes commits in a repository, you may want to notify
your CI server to start a build.
* Every time a user pushes commits or creates a pull request, you may want to
display a notification in your application.
name: webhooks
- description: |
Commit statuses provide a way to tag commits with meta data,
like automated build results.
name: commitstatuses
- description: |
Repository owners and administrators can set branch management
rules on a repository that control what can be pushed by whom.
Through these rules, you can enforce a project or team
workflow. For example, owners or administrators can:
* Limit push powers
* Prevent branch (bookmark) deletion
* Prevent history re-writes (Git only)
name: branchrestrictions
- description: |
Bitbucket Cloud projects make it easier for teams to focus on
a goal, product, or process by organizing their repositories.
name: projects
- description: |
Bitbucket Pipelines brings continuous delivery to Bitbucket
Cloud, empowering teams with full branching to deployment
visibility and faster feedback loops.
name: pipelines
- description: |
Teams are deploying code faster than ever, thanks to continuous
delivery practices and tools like Bitbucket Pipelines. Bitbucket
Deployments gives teams visibility into their deployment
environments and helps teams to track how far changes have
progressed in their deployment pipeline.
name: deployments
paths:
/repositories/{workspace}/{repo_slug}/branching-model:
get:
description: |-
Return the branching model as applied to the repository. This view is
read-only. The branching model settings can be changed using the
[settings](branching-model/settings#get) API.
The returned object:
1. Always has a `development` property. `development.branch` contains
the actual repository branch object that is considered to be the
`development` branch. `development.branch` will not be present
if it does not exist.
2. Might have a `production` property. `production` will not
be present when `production` is disabled.
`production.branch` contains the actual branch object that is
considered to be the `production` branch. `production.branch` will
not be present if it does not exist.
3. Always has a `branch_types` array which contains all enabled branch
types.
Example body:
```
{
"development": {
"name": "master",
"branch": {
"type": "branch",
"name": "master",
"target": {
"hash": "16dffcb0de1b22e249db6799532074cf32efe80f"
}
},
"use_mainbranch": true
},
"production": {
"name": "production",
"branch": {
"type": "branch",
"name": "production",
"target": {
"hash": "16dffcb0de1b22e249db6799532074cf32efe80f"
}
},
"use_mainbranch": false
},
"branch_types": [
{
"kind": "release",
"prefix": "release/"
},
{
"kind": "hotfix",
"prefix": "hotfix/"
},
{
"kind": "feature",
"prefix": "feature/"
},
{
"kind": "bugfix",
"prefix": "bugfix/"
}
],
"type": "branching_model",
"links": {
"self": {
"href": "https://api.bitbucket.org/.../branching-model"
}
}
}
```
parameters:
- description: |
This can either be the username or the UUID of the account,
surrounded by curly-braces, for example: `{account UUID}`. An account
is either a team or user.
in: path
name: workspace
required: true
schema:
type: string
- description: |
This can either be the repository slug or the UUID of the repository,
surrounded by curly-braces, for example: `{repository UUID}`.
in: path
name: repo_slug
required: true
schema:
type: string
responses:
200:
content:
application/json:
schema:
$ref: '#/components/schemas/branching_model'
description: The branching model object
401:
content:
application/json:
schema:
$ref: '#/components/schemas/error'
description: If the request was not authenticated
403:
content:
application/json:
schema:
$ref: '#/components/schemas/error'
description: If the authenticated user does not have read access to the
repository
404:
content:
application/json:
schema:
$ref: '#/components/schemas/error'
description: If the repository does not exist
security:
- oauth2:
- repository
- basic: []
- api_key: []
tags:
- branching_model
x-tags:
- tag: branching_model
/repositories/{workspace}/{repo_slug}/commit/{commit}/properties/{app_key}/{property_name}:
delete:
description: Delete an application property value stored against a commit.
operationId: deleteCommitHostedPropertyValue
parameters:
- description: The account.
in: path
name: workspace
required: true
schema:
type: string
- description: The repository.
in: path
name: repo_slug
required: true
schema:
type: string
- description: The commit.
in: path
name: commit
required: true
schema:
type: string
- description: The key of the Connect app.
in: path
name: app_key
required: true
schema:
type: string
- description: The name of the property.
in: path
name: property_name
required: true
schema:
type: string
responses:
204:
content: {}
description: An empty response.
tags:
- properties
x-tags:
- tag: properties
get:
description: Retrieve an application property value stored against a commit.
operationId: getCommitHostedPropertyValue
parameters:
- description: The account.
in: path
name: workspace
required: true
schema:
type: string
- description: The repository.
in: path
name: repo_slug
required: true
schema:
type: string
- description: The commit.
in: path
name: commit
required: true
schema:
type: string
- description: The key of the Connect app.
in: path
name: app_key
required: true
schema:
type: string
- description: The name of the property.
in: path
name: property_name
required: true
schema:
type: string
responses:
200:
content: {}
description: The value of the property.
tags:
- properties
x-tags:
- tag: properties
put:
description: Update an application property value stored against a commit.
operationId: updateCommitHostedPropertyValue
parameters:
- description: The account.
in: path
name: workspace
required: true
schema:
type: string
- description: The repository.
in: path
name: repo_slug
required: true
schema:
type: string
- description: The commit.
in: path
name: commit
required: true
schema:
type: string
- description: The key of the Connect app.
in: path
name: app_key
required: true
schema:
type: string
- description: The name of the property.
in: path
name: property_name
required: true
schema:
type: string
responses:
204:
content: {}
description: An empty response.
tags:
- properties
x-tags:
- tag: properties
/user:
get:
description: Returns the currently logged in user.
responses:
200:
content:
application/json:
example:
uuid: '{58021780-82b6-4517-b153-0ae73ce3e4b4}'
account_status: active
links:
followers:
href: https://api.bitbucket.org/2.0/users/example-username/followers
following:
href: https://api.bitbucket.org/2.0/users/example-username/following
html:
href: https://bitbucket.org/example-username/
snippets:
href: https://api.bitbucket.org/2.0/snippets/example-username
self:
href: https://api.bitbucket.org/2.0/users/example-username
avatar:
href: https://bitbucket.org/account/example-username/avatar/
repositories:
href: https://api.bitbucket.org/2.0/repositories/example-username
account_id: 123456:daffbc08-1a80-4bd0-98bf-7997de0a3d10
nickname: example-username
created_on: 2018-06-20T23:17:33.616037+00:00
display_name: Example Username
is_staff: false
username: example-username
type: user
schema:
$ref: '#/components/schemas/user'
description: The current user.
401:
content:
application/json:
schema:
$ref: '#/components/schemas/error'
description: When the request wasn't authenticated.
security:
- oauth2:
- account
- basic: []
- api_key: []
tags:
- users
x-tags:
- tag: users
/repositories/{workspace}/{repo_slug}/downloads/{filename}:
delete:
description: Deletes the specified download artifact from the repository.
parameters:
- in: path
name: workspace
required: true
schema:
type: string
- in: path
name: filename
required: true
schema:
type: string
- in: path
name: repo_slug
required: true
schema:
type: string
responses:
default:
content:
application/json:
schema:
$ref: '#/components/schemas/error'
description: Unexpected error.
security:
- oauth2:
- repository:write
- basic: []
- api_key: []
tags:
- downloads
x-tags:
- tag: downloads
get:
description: |-
Return a redirect to the contents of a download artifact.
This endpoint returns the actual file contents and not the artifact's
metadata.
$ curl -s -L https://api.bitbucket.org/2.0/repositories/evzijst/git-tests/downloads/hello.txt
Hello World
parameters:
- in: path
name: workspace
required: true
schema:
type: string
- in: path
name: filename
required: true
schema:
type: string
- in: path
name: repo_slug
required: true
schema:
type: string
responses:
default:
content:
application/json:
schema:
$ref: '#/components/schemas/error'
description: Unexpected error.
security:
- oauth2:
- repository
- basic: []
- api_key: []
tags:
- downloads
x-tags:
- tag: downloads
/repositories/{workspace}/{repo_slug}/issues/{issue_id}/changes:
get:
description: |-
Returns the list of all changes that have been made to the specified
issue. Changes are returned in chronological order with the oldest
change first.
Each time an issue is edited in the UI or through the API, an immutable
change record is created under the `/issues/123/changes` endpoint. It
also has a comment associated with the change.
Note that this operation is changing significantly, due to privacy changes.
See the [announcement](https://developer.atlassian.com/cloud/bitbucket/bitbucket-api-changes-gdpr/#changes-to-the-issue-changes-api)
for details.
```
$ curl -s https://api.bitbucket.org/2.0/repositories/evzijst/dogslow/issues/1/changes - | jq .
{
"pagelen": 20,
"values": [
{
"changes": {
"priority": {
"new": "trivial",
"old": "major"
},
"assignee": {
"new": "",
"old": "evzijst"
},
"assignee_account_id": {
"new": "",
"old": "557058:c0b72ad0-1cb5-4018-9cdc-0cde8492c443"
},
"kind": {
"new": "enhancement",
"old": "bug"
}
},
"links": {
"self": {
"href": "https://api.bitbucket.org/2.0/repositories/evzijst/dogslow/issues/1/changes/2"
},
"html": {
"href": "https://bitbucket.org/evzijst/dogslow/issues/1#comment-2"
}
},
"issue": {
"links": {
"self": {
"href": "https://api.bitbucket.org/2.0/repositories/evzijst/dogslow/issues/1"
}
},
"type": "issue",
"id": 1,
"repository": {
"links": {
"self": {
"href": "https://api.bitbucket.org/2.0/repositories/evzijst/dogslow"
},
"html": {
"href": "https://bitbucket.org/evzijst/dogslow"
},
"avatar": {
"href": "https://bitbucket.org/evzijst/dogslow/avatar/32/"
}
},
"type": "repository",
"name": "dogslow",
"full_name": "evzijst/dogslow",
"uuid": "{988b17c6-1a47-4e70-84ee-854d5f012bf6}"
},
"title": "Updated title"
},
"created_on": "2018-03-03T00:35:28.353630+00:00",
"user": {
"username": "evzijst",
"nickname": "evzijst",
"display_name": "evzijst",
"type": "user",
"uuid": "{aaa7972b-38af-4fb1-802d-6e3854c95778}",
"links": {
"self": {
"href": "https://api.bitbucket.org/2.0/users/evzijst"
},
"html": {
"href": "https://bitbucket.org/evzijst/"
},
"avatar": {
"href": "https://bitbucket.org/account/evzijst/avatar/32/"
}
}
},
"message": {
"raw": "Removed assignee, changed kind and priority.",
"markup": "markdown",
"html": "<p>Removed assignee, changed kind and priority.</p>",
"type": "rendered"
},
"type": "issue_change",
"id": 2
}
],
"page": 1
}
```
Changes support [filtering and sorting](../../../meta/filtering) that
can be used to search for specific changes. For instance, to see
when an issue transitioned to "resolved":
```
$ curl -s https://api.bitbucket.org/2.0/repositories/site/master/issues/1/changes \
-G --data-urlencode='q=changes.state.new = "resolved"'
```
This resource is only available on repositories that have the issue
tracker enabled.
N.B.
The `changes.assignee` and `changes.assignee_account_id` fields are not
a `user` object. Instead, they contain the raw `username` and
`account_id` of the user. This is to protect the integrity of the audit
log even after a user account gets deleted.
The `changes.assignee` field is deprecated will disappear in the
future. Use `changes.assignee_account_id` instead.
parameters:
- description: |
This can either be the username or the UUID of the account,
surrounded by curly-braces, for example: `{account UUID}`. An account
is either a team or user.
in: path
name: workspace
required: true
schema:
type: string
- description: The issue id
in: path
name: issue_id
required: true
schema:
type: string
- description: |
This can either be the repository slug or the UUID of the repository,
surrounded by curly-braces, for example: `{repository UUID}`.
in: path
name: repo_slug
required: true
schema:
type: string
- description: |2-
Query string to narrow down the response. See
[filtering and sorting](../../../meta/filtering) for details.
in: query
name: q
schema:
type: string
- description: |2
Name of a response property to sort results. See
[filtering and sorting](../../../meta/filtering#query-sort)
for details.
in: query
name: sort
schema:
type: string
responses:
200:
content:
application/json:
schema:
$ref: '#/components/schemas/paginated_log_entries'
description: Returns all the issue changes that were made on the specified
issue.
404:
content:
application/json:
schema:
$ref: '#/components/schemas/error'
description: The specified repository or issue does not exist or does not
have the issue tracker enabled.
security:
- oauth2:
- issue
- basic: []
- api_key: []
tags:
- issue_tracker
x-tags:
- tag: issue_tracker
post:
description: |-
Makes a change to the specified issue.
For example, to change an issue's state and assignee, create a new
change object that modifies these fields:
```
curl https://api.bitbucket.org/2.0/site/master/issues/1234/changes \
-s -u evzijst -X POST -H "Content-Type: application/json" \
-d '{
"changes": {
"assignee_account_id": {
"new": "557058:c0b72ad0-1cb5-4018-9cdc-0cde8492c443"
},
"state": {
"new": 'resolved"
}
}
"message": {
"raw": "This is now resolved."
}
}'
```
The above example also includes a custom comment to go alongside the
change. This comment will also be visible on the issue page in the UI.
The fields of the `changes` object are strings, not objects. This
allows for immutable change log records, even after user accounts,
milestones, or other objects recorded in a change entry, get renamed or
deleted.
The `assignee_account_id` field stores the account id. When POSTing a
new change and changing the assignee, the client should therefore use
the user's account_id in the `changes.assignee_account_id.new` field.
This call requires authentication. Private repositories or private
issue trackers require the caller to authenticate with an account that
has appropriate authorization.
parameters:
- description: |
This can either be the username or the UUID of the account,
surrounded by curly-braces, for example: `{account UUID}`. An account
is either a team or user.
in: path
name: workspace
required: true
schema:
type: string
- description: The issue id
in: path
name: issue_id
required: true
schema:
type: string
- description: |
This can either be the repository slug or the UUID of the repository,
surrounded by curly-braces, for example: `{repository UUID}`.
in: path
name: repo_slug
required: true
schema:
type: string
requestBody:
content:
application/json:
schema:
$ref: '#/components/schemas/issue_change'
description: The new issue state change. The only required elements are `changes.[].new`.
All other elements can be omitted from the body.
required: true
responses:
201:
content:
application/json:
schema:
$ref: '#/components/schemas/issue_change'
description: The newly created issue change.
headers:
Location:
description: The (absolute) URL of the newly created issue change.
schema:
type: string
401:
content:
application/json:
schema:
$ref: '#/components/schemas/error'
description: When the request wasn't authenticated.
403:
content:
application/json:
schema:
$ref: '#/components/schemas/error'
description: When the authenticated user isn't authorized to modify the
issue.
404:
content:
application/json:
schema:
$ref: '#/components/schemas/error'
description: The specified repository or issue does not exist or does not
have the issue tracker enabled.
security:
- oauth2:
- issue:write
- basic: []
- api_key: []
tags:
- issue_tracker
x-tags:
- tag: issue_tracker
/repositories/{workspace}/{repo_slug}/patch/{spec}:
get:
description: |-
Produces a raw patch for a single commit (diffed against its first
parent), or a patch-series for a revspec of 2 commits (e.g.
`3a8b42..9ff173` where the first commit represents the source and the
second commit the destination).
In case of the latter (diffing a revspec), a patch series is returned
for the commits on the source branch (`3a8b42` and its ancestors in
our example). For Mercurial, a single patch is returned that combines
the changes of all commits on the source branch.
While similar to diffs, patches:
* Have a commit header (username, commit message, etc)
* Do not support the `path=foo/bar.py` query parameter
The raw patch is returned as-is, in whatever encoding the files in the
repository use. It is not decoded into unicode. As such, the
content-type is `text/plain`.
parameters:
- in: path
name: workspace
required: true
schema:
type: string
- in: path
name: spec
required: true
schema:
type: string
- in: path
name: repo_slug
required: true
schema:
type: string
responses:
200:
content: {}
description: The raw patches
555:
content:
application/json:
schema:
$ref: '#/components/schemas/error'
description: |-
If the diff was too large and timed out.
Since this endpoint does not employ any form of pagination, but
instead returns the diff as a single document, it can run into
trouble on very large diffs. If Bitbucket times out in cases
like these, a 555 status code is returned.
security:
- oauth2:
- repository
- basic: []
- api_key: []
tags:
- commits
x-tags:
- tag: commits
/users/{username}/members:
get:
description: |-
Returns all members of the specified team. Any member of any of the
team's groups is considered a member of the team. This includes users
in groups that may not actually have access to any of the team's
repositories.
This operation has been deprecated due to privacy changes.
See the [announcement](https://developer.atlassian.com/cloud/bitbucket/bitbucket-api-changes-gdpr/)
for details.
parameters:
- in: path
name: username
required: true
schema:
type: string
responses:
200:
content:
application/json:
example:
uuid: '{58021780-82b6-4517-b153-0ae73ce3e4b4}'
nickname: example-username
links:
html:
href: https://bitbucket.org/example-username/
self:
href: https://api.bitbucket.org/2.0/users/example-username
avatar:
href: https://bitbucket.org/account/example-username/avatar/
account_id: 123456:daffbc08-1a80-4bd0-98bf-7997de0a3d10
account_status: active
type: user
username: example-username
display_name: Example Username
schema:
$ref: '#/components/schemas/user'
description: All members
404:
content:
application/json:
schema:
$ref: '#/components/schemas/error'
description: When the team does not exist, or multiple teams with the same
name exist that differ only in casing and the URL did not match the exact
casing of a particular one.
security:
- oauth2:
- account
- basic: []
- api_key: []
tags:
- teams
x-tags:
- tag: teams
/repositories/{workspace}/{repo_slug}/pullrequests/{pull_request_id}/comments/{comment_id}:
delete:
description: Deletes a specific pull request comment.
parameters:
- in: path
name: workspace
required: true
schema:
type: string
- in: path
name: pull_request_id
required: true
schema:
type: string
- in: path
name: comment_id
required: true
schema:
type: string
- in: path
name: repo_slug
required: true
schema:
type: string
responses:
204:
content: {}
description: Successful deletion.
403:
content:
application/json:
schema:
$ref: '#/components/schemas/error'
description: If the authenticated user does not have access to delete the
pull request.
404:
content:
application/json:
schema:
$ref: '#/components/schemas/error'
description: If the pull request does not exist.
security:
- oauth2:
- pullrequest
- basic: []
- api_key: []
tags:
- pullrequests
x-tags:
- tag: pullrequests
get:
description: Returns a specific pull request comment.
parameters:
- in: path
name: workspace
required: true
schema:
type: string
- in: path
name: pull_request_id
required: true
schema:
type: string
- in: path
name: comment_id
required: true
schema:
type: string
- in: path
name: repo_slug
required: true
schema:
type: string
responses:
200:
content:
application/json:
schema:
$ref: '#/components/schemas/paginated_pullrequest_comments'
description: The comment.
403:
content:
application/json:
schema:
$ref: '#/components/schemas/error'
description: If the authenticated user does not have access to the pull
request.
404:
content:
application/json: