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.

I came across an issue where someone deleted a BitBucket automatic merge failure request instead of resolving it. The when another person tried to merge their changes into master, they ended up getting a conflict PR with all the changes (and more) that the other person had in their deleted automatic merge failure PR. Does BitBucket create a branch when a merge conflict occurs? How does it keep track of the merge conflict that seems to remains when the automatic merge failure PR is deleted?

I have cloned the repo with https with my username and password as [discussed here][1] in this format:

I have master branch for a repo in bitbucket which was last updated back in 2017.Now i have a task to sync the latest release branch with master and need to bring all code from release into master.

We are seeing a difference in git on windows and ubuntu when fetching from bitbucket.

Git seems to consider a few newly added files in the repository as copies, and it messes up the diff shown in the PR on bitbucket (as it now shows a fully new file as a changed diff of an existing file).