I would suggest there are two ways to achieve this workflow in Stash.
1. Fork based. A dictator would be the only person permissioned to write to the core repository. Lieutenants would have their own forks, when they the think the code is ready to go the lieutenant would create a pull request from their fork to the core repository for the dictator to review/approve. Regular developers would follow the same method submitting from their forks to the lieutenant's fork.
2. Branch based. In Stash you can restrict writing to certain branches. So again you can have a set of core branches (master, develop, production etc) owned by the dictator and a set of feature branches owned by lieutenants (feature/user-management etc) with developers creating their own story branches (JIRA-123/user-picker).
The keys features of both are controlling access via permissions at the repository/branch level and creating pull requests to promote your work to the next level.
Personally I feel that the branch based model is easier to work with and understand.
Hope that helps,
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