-
Suggestion
-
Resolution: Done
-
2
-
12
-
colored textIt's currently not possible to automatically build pull-requests when they are created from a fork.
- duplicates
-
- Closed
- mentioned in
-
Page Failed to load
-
Page Failed to load
-
Page Failed to load
-
Page Failed to load
-
Page Loading...
-
-
-
-
-
-
-
-
[BAM-14844] Automatic build pull-requests from fork
We also need these feature. In case of many projects / repositories owned by different teams without this feature the permissions management is getting to be hard, it threatens future all permissions became to be a "mesh".
Would like to add my interest to this issue. Building a pull request from a fork is a much needed feature.
Much needed feature, Is this in the plan to pick up ?
Advertising the "build pull-request" feature while it does not work from forks could be considered as a bug, or even a scam.
Issue has been open for >6 years. Last comment from Atlasian is >1 year ago. Very hard to understand, especially since this doesn't look like the most complicate feature to implement.
@Atlassian, could you please update this issue's status? (with something more meaningful than "We'll review this request in about 6 months".)
without this feature forking within Bitbucket is useless for most projects. for me as customer lack of the feature inside bamboo should be considered as a bug of pull-request-feature of the Atlassian suite (jira+bitbucket+bamboo)
Code collaboration with Git
85% of software teams use a distributed version control system, like Git. Git offers a collaborative way to work on code regardless of location. With Bitbucket, teams can see active branches and pull requests while discussing issues where they matter most - leaving inline comments directly in the source code.
Source: https://www.atlassian.com/teams/software
// code placeholder
Definitely hopping over to GitHub. Testing is incredibly important to the stability of our code. Without the ability to ensure that code is passing more involved tests (that may take longer than git hook initiated tests), it's becoming too cumbersome to continue to use Jira + Bamboo.
Edit: Moving over to Gitlab instead, actually.
Same here. We are considering GitHub now as we cannot have proper PR testing when using the GitFlow workflow, that we do use for our largest projects. It is not amazing...
Hi everyone,
Thanks for your interest in this issue.
This request is considered a potential addition to our longer-term roadmap.
We'll typically review this request in about 6 months time, at which point we’ll consider whether we need to alter its status.
For the nearest future we've decided to prioritise other areas of the Bamboo roadmap, including:
- Robustness of Plan Branches
- Performance and stability improvements
- Providing building blocks for High Availability and Disaster Recovery solutions
- Improving permission system
- Allowing per-project allocation of resources
- Improving Bitbucket Server and Jira integrations
You can learn more about our approach to highly voted server suggestions here.
To learn more on how your suggestions are reviewed, see our updated workflow for server feature suggestions.
Kind regards,
Bamboo Team
This feature needs to be implemented as majority of our work is done using the forked repo workflow. It is a major hinderance to not be able to run pipelines on PRs created using forked repos. GitHub does not have this problem. So, please address the gap ASAP.