![]() ![]() When you file a pull request, all you’re doing is requesting that another developer (e.g., the project maintainer) pulls a branch from your repository into their repository. Pull requests put all of this functionality into a friendly web interface right next to your Bitbucket repositories. This can become haphazard, especially when follow-up commits are involved. SVN and Git can both automatically send notification emails with a simple script however, when it comes to discussing changes, developers typically have to rely on email threads. All of this activity is tracked directly inside of the pull request.Ĭompared to other collaboration models, this formal solution for sharing commits makes for a much more streamlined workflow. If there are any problems with the changes, teammates can post feedback in the pull request and even tweak the feature by pushing follow-up commits. ![]() This lets everybody involved know that they need to review the code and merge it into the main branch.īut, the pull request is more than just a notification-it’s a dedicated forum for discussing the proposed feature. Once their feature branch is ready, the developer files a pull request via their Bitbucket account. In their simplest form, pull requests are a mechanism for a developer to notify team members that they have completed a feature. They provide a user-friendly web interface for discussing proposed changes before integrating them into the official project. Pull requests are a feature that makes it easier for developers to collaborate using Bitbucket.
0 Comments
Leave a Reply. |