プル リクエストの自動マージ

プル リクエストがマージ可能かどうかを確認するために作業から離れることがどれくらいありますか。プル リクエストの自動マージがあれば、この面倒な監視に貴重な時間を取られることはなくなります。

自動マージでは、プル リクエストをマージする準備ができたときに、ユーザーに代わって Bitbucket にマージさせるかどうかを選択できます。自動マージが可能な場合は、[マージ] ボタンに時計アイコンが表示されます 。

すべてのマージ チェックに合格すると、自動マージのプル リクエストを送信したユーザーに代わって Bitbucket がこのプル リクエストを自動的にマージします 。

プル リクエストの自動マージの詳細を確認する

Define code owners for pull request reviews and shared codebase expertise (releases 8.14)

SERVER DATA CENTER

You can now define owners with expertise for specific areas of the codebase by creating a CODEOWNERS file in your repository. A code owner will be automatically notified about any pull request that introduces changes to the code they’re responsible for. Code owners will also be automatically added to pull requests as reviewers.

Learn more about how to define code owners

Preview and watch videos from pull requests with a web video player (released 8.13)

DATA CENTER

With a built-in video player, you can now preview and watch videos from descriptions and comments in pull requests. If you’re attaching a video file from your own storage to a pull request, make sure that the video meets the following requirements:

• The supported formats are mp4, mov, and webm.

• The maximum file size is 10 Mb.

Discover unsigned commits and inspect committers' identities (released 8.13)

SERVER DATA CENTER

While signing commits with GPG keys has already been available in Bitbucket, you can now check if a commit has a verified signature or not on the Commits page. A quick glance at the page will help you find signed and unsigned commits and identify their authors. So you can always monitor the security of changes to your code and timely react to any suspicious issues.

Custom template for commit messages (released 8.12)

SERVER DATA CENTER

After release 8.12, you can configure a custom template for a commit message. When you merge a pull request, the value set in the template will be used to populate the title and body fields of the commit message in the merge modal. Commit message templates also support variables, allowing your commit messages to include details such as the source and target branch or the approvers of the pull request. 

If the custom template isn’t set, Bitbucket will generate a commit message suggestion for you in the same way it does in previous versions.

この機能は、プルリクエストの標準プラクティスを確立するのに役立ちます。 あなたのチームは、必要な詳細をコピーして貼り付ける時間を無駄にすることなく、一貫性のある有益なコミットメッセージを追加し、有用な Git コミット履歴を作成します。

Learn how to configure commit message templates

Resolve and collapse comments (released 8.9)

SERVER DATA CENTER

When a pull request has lots of comments it becomes hard to navigate and focus on really important discussions. You can now resolve comment threads to communicate to the rest of the pull request participants that the issue has been addressed, the decision has been made, and no further discussion is needed.

If many comments on the pull request are still open and you want to focus on the code diff, you can quickly declutter your view by collapsing comment threads.

Learn how to resolve comments

Diff view updates (released 8.0)

7.0 でプル リクエストを再設計して刷新しました。今回、すべての差分ビュー (コミット差分、ブランチ比較、プル リクエストの作成ページを含む) を新しい形式に移動させました。素早く一貫したコード コラボレーション エクスペリエンスをお楽しみください。

これらのページで、ご利用のアプリや連携機能がフロントエンド プラグインを利用している場合、プル リクエストの更新についてのオリジナル情報で API の変更についてご確認ください。

Reviewer groups for pull requests (released 7.13)

 DATA CENTER

同じレビュアーをプル リクエストに 1 人ずつ追加するために、必要よりも多くの時間を費やしているようなことはありませんか? レビュアー グループを使い、コード レビューに関与する必要がある適切なレビュアーを素早く追加できます。

プル リクエストを作成するときに、レビュアー フィールドにグループ名を入力して、追加するレビュアー グループを選択します。

プロジェクトおよびリポジトリの管理者がレビュアー グループを作成および管理します。これにより、開発チームはこのようなグループを自身で管理できます。プロジェクトまたはリポジトリへのアクセスを持つ既存の Bitbucket ユーザーからグループ メンバーを選択します。

Get more information on how reviewer groups can help speed up your code review workflow.

Pull request description templates (released 7.13)

 DATA CENTER

プル リクエストの説明用のテンプレートを使うことで、時間を節約し、レビュアーはコード レビューで予測すべき内容を確認できます。レビューのガイドラインを伝えたり、完了する必要のある一般的なタスクを作成者に周知したりすることができます。新しいプル リクエストが作成されると、デフォルトの説明テンプレートのコンテンツが使われ、自動的に適用されます。

プル リクエストのための新しい説明テンプレートをプロジェクト設定ページで確認できます。

Update pull requests to the latest version (released 7.10)

SERVER DATA CENTER

コードのレビュー中にプル リクエストが変更されたときに Bitbucket によって通知が表示されるようになりました。これにより、コードを更新して最新の変更を確認できます。

New code review workflow (released 7.7)

SERVER DATA CENTER

As a pull request reviewer, you can now draft multiple comments on files and code during a review process. Then when you are ready, send them all off at once, rather than just one at a time. This new code review workflow will save you time and unnecessary back and forth exchanges with the pull request author.

React to comments (released 7.7)

コメントへの返信が簡単になりました。コメントへのリアクション機能により、任意のコメントに絵文字を追加できるようになりました。素早く 👍 を追加したり、✅ とマークしたり、🔥 を追加したりしたいときに、数クリックで最適な絵文字を挿入できます。

Select the Add reaction buttonto try it out, and see Commenting on a pull request for more information.

Accessible colors for the diff view (released 7.7)

SERVER DATA CENTER

We’ve been hard at work to make some important accessibility changes. This release includes a new setting for the diff view that lets you switch to an accessible color option that uses blue and yellow for added and removed lines respectively. Once enabled, the colors will change immediately in the diff view.

View hidden comments (released 7.4)

SERVER DATA CENTER

No more disappearing act for comments that are in older diffs or that have become outdated due to a pull request update. By selecting the other comment counter when it appears on your pull request, you’ll have more context on why code has changed throughout a pull request by being able to:

• See a file’s activity stream showing comments that are outdated or appear on another diff.

• Distinguish which comments are actually outdated.

• Reply to, like, delete, or react to outdated comments the same way you can from the overview tab.

Locate pull requests by searching for text and selecting a reviewer (released 7.2)

SERVER DATA CENTER

It's not productive to have to sift through a large list of pull requests in order to locate a comment you've left or to see why a change was made, so we've made it easier to find a pull request by refining your search. Quickly filter on matches to pull request titles and their descriptions by entering some text into the new search field. We've also added the option to filter by any reviewer so that you can further narrow down the list of pull requests that you've reviewed.

For information on other pull request filtering options, see Search for pull requests.

Pull requests get a makeover (released 7.0)

SERVER DATA CENTER

The pull request page has been redesigned and packed full of improvements to make your code review experience smoother, more enjoyable, and less of a tedious task.

Faster navigation in pull requests

With twice-as-fast content loading while switching between diffs, improved file navigation performance, and smooth scrolling in a side-by-side diff, you just might find yourself having fun speeding through your code reviews.

A more intuitive design

We've improved the pull request workflow, giving you a more effective and efficient experience.

Better collaboration in the diff view

• Commenting
  • Comment anywhere in the diff, including on expanded lines of code that weren't changed as a part of the pull request.
  • Comment on files stored via Git LFS.
• Syntax highlighting: Until now, syntax highlighting was only available on the side-by-side diff, but now it’s available in the unified diff too.

• Word wrap: No more horizontal scrolling to read lines of code in the diff.
• Expanding: Click Show more to expand all lines in the diff now, rather than just 10 at a time.
• Searching: You can now use your browser’s native Ctrl+F action to search for code in the file you’re viewing.
• Image thumbnails: Drag or attach an image into a comment and you’ll see a thumbnail-sized preview of it rather than having the full-sized image rendered.

Do more with less clicking

• Copying: You can now copy code from just one side of the side-by-side diff view without also copying code from the other one. Also, select and copy branch names in one click.
• Pasting: When you paste code from a pull request into a comment, we’ll automatically format it as a code block with the correct syntax highlighting.
• Editor: When you type into a comment or description editor in a PR, you'll see Markdown hints as you type, no need to preview until you’re ready to see the final view.

File-tree improvements

• Filtering: Easily locate changed files in a pull request using the new Filter file tree button. Use wildcards to find what you need faster on pull requests that have a great deal of files to look through. You can find it just above the file-tree, along with the Search code button. To see an example, check out Reviewing a pull request.
  
  

• Redesigned icons: Icons in the file tree view now have a more distinctive design with contrasting colors so that you can better recognize the relationship between them, and whether your file has been edited, added, removed, or modified.

Task improvements in a pull request (released 7.0)

SERVER DATA CENTER

Create tasks in your pull requests without having to write a comment first. In fact, you can even convert comments into tasks. They also now support Markdown and rich content, like code snippets. Check the Reviewing a pull request page for more details.

We've got your code covered (released 7.0)

SERVER DATA CENTER

Code Insights for Bitbucket offers a better way for your team to improve code quality by allowing continuous integration (CI) and other analysis tools to surface insights about code quality in pull requests. This is so issues that are related to code quality can be viewed and acted upon during a normal code review process. Now, you can access your code coverage results as a part of Code Insights.

Code coverage finds aspects of the code which may not have been covered adequately by tests. The results are compiled and displayed in the diff view using color-coded blocks which represent lines of code that are covered fully, partially, or not at all by tests. You can then also dig into a coverage report, if it’s provided, to see the actual lines that may not be covered and use that to identify critical parts of your application that still need to be tested.