Its possible to use the way that you prefer, but in my personal opinion to organize better your programs/projects I’ll recommend a repository for each program.
To help you better there is also the Atlassian Bitbucket documentation as you can see on the following link:
I hope this information could be useful.
I'd also prefer a repository per program to a repository per project. This will mean a (potentially) lot of smallish repositories instead of one (potentially) gigantic repository. As we don't know the details of your project and programs it's impossible to say for sure which way suits you better.
Because Bitbucket is missing a way to group repositories I've implemented a simple repository naming convention:
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