Trying to understand why it works.

We have a scenario where we have multiple layers of branches that all need to auto-merge

In our team, the usual workflow to work on features is, we have a develop branch in our main repo, and each developer creates their own fork. When developing, each developer creates a feature branch in their fork and raise PR to the develop branch on the main repo.

We have a number of main branches in our git repositories:

We have a number of main branches in our git repositories:

Our repo has pre commit hooks that enforce conventional commits on a push, but we can’t figure out a way to enforce conventional commits on a squash commit to main/master in the Bitbucket Cloud.

Could a rogue developer “delete” source code from a hosted git repo (bitbucket) by merging a PR which rewrites history, so would not be un-doable?

The question is about storing git configs as part of a repository. In the top answer, some very helpful individuals have laid out how to create a custom git config and include it in the path for a single repo. The one issue I have with this is that the commands they outline – git config --local include.path ../.gitconfig – seemingly need to be run every single time the repository is cloned in order to make use of the aliases within it.

I’m creating a custom sharedgitconfig file in one of the repositories of a project in bitbucket based on what I was able to read here. I’m a beginner, so please bear with me if these questions are fairly basic. The idea is that this repository will be cloned initially, and the developers will be able to use the infrastructure to make their changes to the code before using git aliases to automate some of the more tedious commands and naming schemes we have in place for things like Jenkins.

My local repository is considerably smaller than remote repo on bitbucket(~800 megabytes locally and 3.8 gigs on the remote). This is an issue because my repository is about to hit 4gb limit, after which further commits will not be possible.