Hi Prayuja,
If the source branch of the pull request is in the same repository you can simply clone the repository as it will contain the branch with the changes the pull request is proposing to merge. If the source branch is in another repository (for instance a fork of the target repository), then you'll need to clone that repository (instead or in addition)
The pull request itself is metadata not stored in the repository but in Bitbucket Server's database.
Cheers,
Christian
Premier Support Engineer
Atlassian
Bitbucket promotes the methodology of personal repo-forking of a project, and upstream PRs for submissions.
For a private repo (the vast majority of cases for this kind of usage), then each fork would also be a private repo.
Code reviewing a PR becomes a tooth-pulling nightmare, especially with regards to SSH authentication. Each team member would need to add each other as a contributor combined with SSH Authentication - *for EACH and every project within the project!*. The current team I'm now part of, that would mean 25 * 75 (1875) instances that this would need to be done, instead of a simple command like:
git fetch origin pull/1234/head
# or
git config --add remote.upstream.fetch '+refs/pull-requests/*/from:refs/remotes/upstream/pr/*'
git fetch upstream
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.