However, as reviewers look at your code and make comments, you'll receive email notifications of the ongoing discussion in the pull request, giving you an opportunity to respond and making you become an active participant in the code review process. If you don't add reviewers during creation, you can always edit the pull request to add them afterwards.Īfter you've created a pull request and added reviewers, you might be inclined to take a break while you wait for approvals. To find pull requests you've created, check the Your pull requests list on the Your work dashboard.Īs a pull request author, the code review process officially begins after you create the pull request with reviewers. The following is an illustration of how the end-to-end pull request process works. Pull request processĬode review and collaboration are at the core of pull requests. Depending on your role, you may be an author, a reviewer, or both on one or more pull requests. You can see how pull requests fit into a larger workflow example on the Workflow for Git feature branching help document. To use pull requests, you need a branch or a fork, so you can develop your code on a separate branch (line) from the main code base.
Pull requests provide you with a method for requesting code reviews from your colleagues and checking build status based on your most recent commit. To get the feedback you need for code updates and improvements, you can create a pull request that includes all the lines of code you've added. Before you merge, you want to ensure that you maintain code quality and won't break already existing features. After you've added files and made updates to existing code, it's time to merge that code into your Bitbucket Cloud repository.
0 kommentar(er)
