In order to facilitate feature development with multiple developers, the most efficient/effective way to do it is to fork the product repo, then have each individual developer for the fork, work on it, and do pull requests into the first fork. Once the the feature is done, the top-level fork could be PR'ed back into the main project repo.
This is not unlike a feature-branch model, but we prefer not to use that model because 1) it clutters the repo with unnecessary branches and 2) it keeps each repo in sync via fork-synching, whereas a feature-branch can and will fall behind.
So - my ask is that Stash/Bitbucket provide the ability to fork a fork
Yes you can fork a fork. One thing to be aware of is if your repository has submodules those will need special handling. If you can use relative paths for the submodule URL then it will be possible to fork the repository and the submodules it contains without any problems. If you never want to fork the submodule then you don't need to worry about using relative paths.
Bitbucket Pipelines helps me manage and automate a number of serverless deployments to AWS Lambda and this is how I do it. I'm building Node.js Lambda functions using node-lambda ...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
We're bringing product updates and pro tips on teamwork to ten cities around the world.Save your spot