Git Scheme - How Optimal Is My Scheme?

Question

git

Actually, I’ll tell you my scheme of working on a project, I’ve been using git for a while, I would like to understand how optimal this work is, where there are vulnerabilities. In general, a question for experienced git'ers.
On the example of kohana (I still won’t switch to something modern :)) ).
1. First I clone the kohana repository.
2. I connect all the necessary submodules, etc. I'm setting up all this shit ... business, I'm sorry
3. Next, I push the repository to bitbucket.
4. I create another folder for testing on the server next to it, I clone the newly created repository there.
5. It turns out the main domain. ru - site here, dev.main domain. ru - here is the development branch.
6. I make branches for each problem and feature in the dev version, periodically push everything to bitbucket, when it is stable (merged with solved problems) the pool into the main branch.
In fact, you can exclude the bitbucket from the chain and push directly to the combat project, I think .. But if I work with the team, they will be able to pull everything from the bitbucket and not go into my dev.domain stuff ... (a little selfish, mb. but I don’t want to deploy a web server on my laptop)
What will the pros say? Where are the bottlenecks, or is everything okay?

Answer 1

If you are completely satisfied with your scheme - it is optimal.

Answer 2

you invented feature branches
No, git is not a deployment tool.

Answer 3

If I understood correctly, then you will be interested in the link