Bitbucket

What I liked the most about using Bitbucket was the possibility of interconnecting everything from JIRA and Confluence directly and seamlessly to my repositories. This helped my team not only to save time but also to keep track of everything happening around our development cycle in a way that felt natural.

The interface tries to differentiate from GitHub a lot, and sometimes it feels it is not something you need to innovate into; some things are just the way they are. I found the project->repository structure confusing, and navigating through them wasn't easy.

Probably the integration with the complete Atlassian suite is what attracts me the most, working with Jira, Trello, Confluence and being able to solve problems from a support or customer service common to all these applications, greatly influences the decision to work with Bitbucket.

Well, there are two clear competitors that take the majority of the repositories, but they are not mutually exclusive, you can use another of them, perhaps better in some aspects, while still taking advantage of the integration with the other applications.

there are several aspects of Bitbucket that I found particularly impressive and impactful. Firstly, what I liked most about Bitbucket was its seamless integration with our development workflow. The ability to create and manage repositories, branches, and pull requests directly within Bitbucket simplified our code collaboration process significantly.One of the most impactful features of Bitbucket was its robust version control system. The ability to track changes, revert to previous versions, and compare different branches made it easy for us to manage our codebase effectivelyThe integration of Bitbucket with our existing business infrastructure was relatively straightforward. Overall, Bitbucket proved to be an invaluable tool for our web development projects.

While Bitbucket has been an invaluable tool for our web development projects, there were a few aspects that could be improved uponwe occasionally encountered difficulties when configuring complex CI/CD pipelines within Bitbucket. While the basic configuration was straightforward, more intricate setups or customizations required additional effort and expertiseOne aspect I found limiting was the lack of customization options for the user interface. Bitbucket's interface is functional, but it would be beneficial to have more flexibility in customizing the layout, color schemes, or overall visual appearance to suit individual preferences or align with specific branding requirementsIt's important to note that while these were the aspects we liked least about Bitbucket, they did not significantly hinder our overall experience with the platform

Bitbucket has a very friendly interface that is easy to understand and understand, it allows you to maintain control and order of all your elements and keep track of each modification that was made and by whom said modification was made.
It allows you to establish different types of permissions as necessary to have a better control of who can perform what actions within the repositories that are created in bitbucket.
Once you get familiar with the tool, everything is easy to do and locate any option you are looking for to carry out your tasks.

Sometimes the way it provides you to search within each repository can be somewhat cumbersome, requiring you to write the exact name of the component you may be looking for in order to show you a result, making the searches more strenuous since you must know the exact name of the component or it will be very difficult to find it.
In some cases, when versioning certain changes, Bitbucket interprets them as a total change within the component and shows as if the file was being completely modified even if you are only modifying some lines of code.