Skip to main content

2 min read

3 simple ways to master your Git repositories

3 simple ways to master your Git repositories
alert2 Icon
The content of this blog is no longer updated

3 simple ways to master your Git repositories

Git repositories, just like documentation or file systems, can get messy. There are a lot of moving pieces; different projects being developed quickly and many people working on the same things. Establishing a set of best practices is critical to the effectiveness of your Git repositories.

We felt that good Git practice is so important that we developed an app that can help monitor Bitbucket. Here are three ways you can better manage, protect, and enforce standards using ScriptRunner for Bitbucket.

Keep your branches up to date

Working in a team with multiple projects can result in pull requests taking quite a long time to be merged. That results in branches falling behind the master, which is not ideal. A branch too far out of date can take a ridiculously long time to merge while you sit and twiddle your thumbs. However, you can use ScriptRunner for Bitbucket to warn users how many commits their branch is behind. So large, time-consuming merge conflicts can be avoided.

Pull Request Advisor

Read more on our documentation.

Standardise and enforce naming

There's a reason that companies adopt naming standards. Standardising allows for better organisation and tracking of pull requests, in addition to aiding traceability of work.

Bitbucket natively comes with the ability to include the prefixes onto different types of pull requests (bugs, features and releases), but ScriptRunner for Bitbucket enables you to automatically begin pull requests with preset variables or change request IDs as well. This results in more granular and detailed pull request name types.

Naming standard enforcement

Check out using branches in Bitbucket on the Confluence support site.

Track every branch in one place

As you develop, it's important to make sure every single branch is tracked in Jira. The last thing any developer wants to run into is a surprise bit of code that starts breaking things when you mess with it. Again, ScriptRunner for Bitbucket can help by ensuring all branches are tracked in Jira. So if, in the future, you need to refer back to something, you have enforced traceability. Nothing gets past you and ScriptRunner for Bitbucket.

Commits for Jira

These are just three ways ScriptRunner for Bitbucket can improve your work, but we've barely scratched the surface. To find out what else ScriptRunner for Bitbucket has up it's sleeve, start your free trial today.

copy_text Icon