VS Code extension and bitbucket.org parity

[Matthew Brown]

I'm not sure if a goal is some amount of parity between the VS Code extension and bitbucket.org, but here are a couple discrepancies I noticed when submitting my latest PR:

1. By default, bitbucket.org is using my commit message as the title and the extension is using my branch name
2. bitbucket.org has pre-populated the Reviewers and the extension defaults to blank

‌

• VS Code: v1.39.0 (user setup)
• Atlascode: v2.1.0
• Client OS: Windows 10 1903

‌

[Alastair Wilkes]

Hi Matthew,

Yes, we aim for the extension to work in a similar fashion where possible. These two examples are definitely areas we can and should be consistent.

1. By default, bitbucket.org is using my commit message as the title and the extension is using my branch name

Good catch; we can make these consistent. I've opened #238 for this.

2. bitbucket.org has pre-populated the Reviewers and the extension defaults to blank

Hmm -- this should already be working. If the reviewers field is not being populated with the repository's default reviewers, would you mind opening a separate bug for that?

(I'm closing this because these problems are now tracked elsewhere.)

Thanks!
Alastair