You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
A bug has been reported in issue #${{ github.event.issue.number }}.
31
+
32
+
Issue title: ${{ github.event.issue.title }}
33
+
Issue body:
34
+
${{ github.event.issue.body }}
35
+
36
+
Please do the following:
37
+
1. Analyze the issue carefully to understand the bug being reported.
38
+
2. Explore the codebase to find the relevant code that is likely causing the bug.
39
+
3. Implement a fix for the bug.
40
+
4. Create a new branch named `fix/issue-${{ github.event.issue.number }}` from main.
41
+
5. Commit your changes to that branch with a descriptive commit message.
42
+
6. Open a **draft** pull request targeting the main branch with:
43
+
- A clear title summarizing the fix
44
+
- A description explaining what the bug was and how you fixed it
45
+
- `Fixes #${{ github.event.issue.number }}` in the PR body
46
+
47
+
Important guidelines:
48
+
- Only change code that is directly related to fixing the reported bug. Do not refactor or make unrelated improvements.
49
+
- If you cannot determine the root cause or the fix is too risky/complex, leave a comment on the issue explaining what you found and why an automated fix isn't appropriate.
50
+
- Make sure the fix is complete and the code compiles/passes linting before opening the PR.
Copy file name to clipboardExpand all lines: CHANGELOG.md
+29Lines changed: 29 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -7,6 +7,35 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
7
7
8
8
## [Unreleased]
9
9
10
+
### Added
11
+
- Added PostHog events for chat UI interactions (details card expand/collapse, copy answer, table of contents toggle) and repo tracking in `wa_chat_message_sent`. [#922](https://github.com/sourcebot-dev/sourcebot/pull/922)
12
+
- Added Bitbucket Cloud OAuth identity provider support (`provider: "bitbucket-cloud"`) for SSO and account-linked permission syncing. [#924](https://github.com/sourcebot-dev/sourcebot/pull/924)
13
+
- Added permission syncing support for Bitbucket Cloud. [#925](https://github.com/sourcebot-dev/sourcebot/pull/925)
14
+
15
+
### Changed
16
+
- Hide version upgrade toast for askgithub deployment (`EXPERIMENT_ASK_GH_ENABLED`). [#931](https://github.com/sourcebot-dev/sourcebot/pull/931)
17
+
18
+
### Fixed
19
+
- Fixed text inside angle brackets (e.g., `<id>`) being hidden in chat prompt display due to HTML parsing. [#929](https://github.com/sourcebot-dev/sourcebot/pull/929)[#932](https://github.com/sourcebot-dev/sourcebot/pull/932)
20
+
21
+
## [4.11.7] - 2026-02-23
22
+
23
+
### Changed
24
+
- Skip redundant dev build when production release commits are pushed to main. [#919](https://github.com/sourcebot-dev/sourcebot/pull/919)
- Added GitHub workflow to automatically tag Linear issues with the release version when a new release is published. [#917](https://github.com/sourcebot-dev/sourcebot/pull/917)
31
+
- Added optional `gitUser` field to the Bitbucket connection config to support Bitbucket Cloud API tokens, which require an email address for the REST API but an Atlassian username for git clone. [#918](https://github.com/sourcebot-dev/sourcebot/pull/918)
32
+
33
+
## [4.11.5] - 2026-02-21
34
+
35
+
### Fixed
36
+
- Skip calling `getCommitHashForRefName` for empty repositories to avoid noisy debug log output. [#914](https://github.com/sourcebot-dev/sourcebot/pull/914)
37
+
- Fixed "Open in GitLab" links having a double slash when the GitLab host URL is configured with a trailing slash. [#915](https://github.com/sourcebot-dev/sourcebot/pull/915)
A Bitbucket Cloud connection can be used for [authentication](/docs/configuration/auth) and/or [permission syncing](/docs/features/permission-syncing). This is controlled using the `purpose` field
173
+
in the Bitbucket Cloud identity provider config.
174
+
175
+
<Accordiontitle="instructions">
176
+
<Steps>
177
+
<Steptitle="Register an OAuth Consumer">
178
+
To begin, you must register an OAuth consumer in Bitbucket to facilitate the identity provider connection.
179
+
180
+
Navigate to your Bitbucket workspace settings at `https://bitbucket.org/<your-workspace>/workspace/settings/api` and create a new **OAuth consumer** under the **OAuth consumers** section.
181
+
182
+
When configuring your consumer:
183
+
- Set the callback URL to `<sourcebot_url>/api/auth/callback/bitbucket-cloud` (ex. https://sourcebot.coolcorp.com/api/auth/callback/bitbucket-cloud)
184
+
- Enable **Account: Read**
185
+
- If using for permission syncing, also enable **Repositories: Read**
186
+
187
+
The result of creating an OAuth consumer is a `Key` (`CLIENT_ID`) and `Secret` (`CLIENT_SECRET`) which you'll provide to Sourcebot.
188
+
</Step>
189
+
<Steptitle="Define environment variables">
190
+
To provide Sourcebot the client id and secret for your OAuth consumer you must set them as environment variables. These can be named whatever you like
191
+
(ex. `BITBUCKET_CLOUD_IDENTITY_PROVIDER_CLIENT_ID` and `BITBUCKET_CLOUD_IDENTITY_PROVIDER_CLIENT_SECRET`)
192
+
</Step>
193
+
<Steptitle="Define the identity provider config">
194
+
Finally, pass the client id and secret to Sourcebot by defining a `identityProvider` object in the [config file](/docs/configuration/config-file):
@@ -78,25 +76,107 @@ If you're not familiar with Sourcebot [connections](/docs/connections/overview),
78
76
79
77
## Authenticating with Bitbucket Cloud
80
78
81
-
In order to index private repositories, you'll need to provide authentication credentials via a [token](/docs/configuration/config-file#tokens). You can do this using an `App Password` or an `Access Token`
79
+
In order to index private repositories, you'll need to provide authentication credentials via a [token](/docs/configuration/config-file#tokens). You can do this using an `API Token`, `Access Token`, or `App Password`.
82
80
83
81
<Tabs>
84
-
<Tabtitle="App Password">
85
-
Navigate to the [app password creation page](https://bitbucket.org/account/settings/app-passwords/) and create an app password. Ensure that it has the proper permissions for the scope
86
-
of info you want to fetch (i.e. workspace, project, and/or repo level)
Next, provide your username + app password pair to Sourcebot:
90
-
91
-
<BitbucketAppPassword />
82
+
<Tabtitle="API Token">
83
+
1. Navigate to [Personal Settings → API tokens](https://id.atlassian.com/manage-profile/security/api-tokens) and click **Create API token with scopes**. Give the token a name and set an expiry date.
84
+
85
+
2. Select **Bitbucket** as the app.
86
+
87
+
3. Select the following scopes:
88
+
-`read:repository:bitbucket` — View your repositories
89
+
-`read:workspace:bitbucket` — View your workspaces
90
+
91
+
4. Click **Create token** and copy the token value.
92
+
93
+
5. Add the `user` (your account email), `gitUser` (your Bitbucket username), and `token` to your connection config. [Learn why both are needed](https://support.atlassian.com/bitbucket-cloud/docs/using-api-tokens/)
94
+
95
+
```json
96
+
{
97
+
"type": "bitbucket",
98
+
"deploymentType": "cloud",
99
+
"user": "you@example.com",
100
+
"gitUser": "myusername",
101
+
"token": {
102
+
// note: this env var can be named anything. It
103
+
// doesn't need to be `BITBUCKET_TOKEN`.
104
+
"env": "BITBUCKET_TOKEN"
105
+
}
106
+
// .. rest of config ..
107
+
}
108
+
```
109
+
110
+
6. Pass this environment variable each time you run Sourcebot:
111
+
112
+
```bash
113
+
docker run \
114
+
-e BITBUCKET_TOKEN=<API_TOKEN> \
115
+
/* additional args */ \
116
+
ghcr.io/sourcebot-dev/sourcebot:latest
117
+
```
92
118
</Tab>
93
119
<Tabtitle="Access Token">
94
120
Create an access token for the desired scope (repo, project, or workspace). Visit the official [Bitbucket Cloud docs](https://support.atlassian.com/bitbucket-cloud/docs/access-tokens/)
95
121
for more info.
96
122
97
-
Next, provide the access token to Sourcebot:
123
+
1. Add the `token` property to your connection config:
124
+
125
+
```json
126
+
{
127
+
"type": "bitbucket",
128
+
"deploymentType": "cloud",
129
+
"token": {
130
+
// note: this env var can be named anything. It
131
+
// doesn't need to be `BITBUCKET_TOKEN`.
132
+
"env": "BITBUCKET_TOKEN"
133
+
}
134
+
// .. rest of config ..
135
+
}
136
+
```
137
+
138
+
2. Pass this environment variable each time you run Sourcebot:
139
+
140
+
```bash
141
+
docker run \
142
+
-e BITBUCKET_TOKEN=<ACCESS_TOKEN> \
143
+
/* additional args */ \
144
+
ghcr.io/sourcebot-dev/sourcebot:latest
145
+
```
146
+
</Tab>
147
+
<Tabtitle="App Password">
148
+
<Warning>
149
+
App Passwords are deprecated. Atlassian recommends migrating to API tokens. [Learn more](https://www.atlassian.com/blog/bitbucket/bitbucket-cloud-transitions-to-api-tokens-enhancing-security-with-app-password-deprecation)
150
+
</Warning>
151
+
152
+
Navigate to the [app password creation page](https://bitbucket.org/account/settings/app-passwords/) and create an app password. Ensure that it has the proper permissions for the scope
153
+
of info you want to fetch (i.e. workspace, project, and/or repo level)
0 commit comments