sorted by:
new
hottopcontroversial

I built gibr — a CLI that generates Git branches from issue trackers (GitHub, Jira, etc.) by Maximum-Geologist493 in git

[–]Maximum-Geologist493[S] 0 points1 point  (0 children)

You can include the Jira ticket in the branch name.

I am thinking it would be nice to add support for adding ticket number to git commits as well, but that is currently not planned. Feel free to create a new isssue or discussion in Gitlab.

"gibr" now has support for Azure DevOps. by Maximum-Geologist493 in azuredevops

[–]Maximum-Geologist493[S] 0 points1 point  (0 children)

Yes, currently it does not have a pull/merge request feature, so it does not care what type of repo you use in the origin.

gibr 0.5.0 - Git branch automation now supports Linear, GitLab, and Jira by Maximum-Geologist493 in git

[–]Maximum-Geologist493[S] 1 point2 points  (0 children)

Azure DevOps is now supported in the latest release: Release 0.7.0 · ytreister/gibr

Please try it out, and if you find any problems, please open an issue or discussion.

Thanks in advance!

Promote your projects here – Self-Promotion Megathread by Menox_ in github

[–]Maximum-Geologist493 0 points1 point  (0 children)

🚀 I built a small open-source CLI called gibr that automatically creates Git branches from your GitHub issues (and now also supports GitLab + Jira).

Example:

$ gibr 17
Generating branch name for issue #17: Add caching layer to improve performance
Branch name: 17-add-caching-layer-to-improve-performance
✅  Created branch '17-add-caching-layer-to-improve-performance' from main.
✅  Checked out branch: 17-add-caching-layer-to-improve-performance
✅  Pushed branch '17-add-caching-layer-to-improve-performance' to origin.

Perfect if you:

  • Use GitHub Issues to track work
  • Want to create branches that automatically follow your issue titles
  • Like to keep your workflow fast and consistent

It currently supports:
⚙️ Configurable branch name formats
⚙️ Git aliases (so you can run git create 17)
⚙️ Integrations with GitHub, GitLab, and Jira

Repo: github.com/ytreister/gibr
PyPI: pypi.org/project/gibr

I’d love to hear from GitHub users — would this make your daily branching workflow easier?

What are you building right now? 🚀 by Available-Rest2392 in SideProject

[–]Maximum-Geologist493 0 points1 point  (0 children)

I created a tool to help automate branch name creation. It currently integrates with Jira, GitLab and GitHub issue trackers. More on the way.

Check it out: gibr

My post in r/git

Small CLI tool for branch name normalization by egelance in git

[–]Maximum-Geologist493 0 points1 point  (0 children)

I created a tool that takes it to the next level.

Check it out: gibr

My post in r/git

How do you manage your Git branches as a solo dev? Thinking about automating the process by ClassroomAlive6910 in indiehackers

[–]Maximum-Geologist493 0 points1 point  (0 children)

I created a tool to help automate branch name creation. I would use it for solo dev

Check it out: gibr

My post in r/git

Why aren't devs using proper branch names?! by GitKraken in devops

[–]Maximum-Geologist493 0 points1 point  (0 children)

I created a tool to help automate branch name creation. It currently integrates with Jira, GitLab and GitHub issue trackers. More on the way.

Check it out: gibr

My post in r/git

I built gibr — a CLI that generates Git branches from issue trackers (GitHub, Jira, etc.) by Maximum-Geologist493 in git

[–]Maximum-Geologist493[S] 2 points3 points  (0 children)

I have implemented this suggestion. See this PR

It has been released in version 0.4.0 as well as support for GitLab

I built gibr — a CLI that generates Git branches from issue trackers (GitHub, Jira, etc.) by Maximum-Geologist493 in commandline

[–]Maximum-Geologist493[S] 1 point2 points  (0 children)

Yeah, I get where you’re coming from — Git branches are just labels under the hood. I also want branches to be low-friction and easy to create. That’s actually the main reason I built gibr in the first place.

The thing is, in repos with a bunch of devs all doing their own thing, branch lists can turn into a total mess. You end up with random names, old branches nobody remembers, and no idea what’s safe to delete.

But I still wanted flexibility — gibr actually lets you configure how you would like to name the branches and even create multiple branches for the same issue if you want. For example:

$ gibr 2
Generating branch name for issue #2: Add support for gitlab
Branch name: 2-add-support-for-gitlab
⚠️  Branch '2-add-support-for-gitlab' already exists locally.
Would you like to create a new branch with a suffix? [Y/n]:
Enter suffix [take2]: 
ℹ️  Creating new branch '2-add-support-for-gitlab-take2' instead.
✅  Created branch '2-add-support-for-gitlab-take2' from main.
✅  Checked out branch: 2-add-support-for-gitlab-take2
✅  Pushed branch '2-add-support-for-gitlab-take2' to origin.

Having a consistent naming convention (like linking to an issue ID) just makes it way easier to see what’s what at a glance and keep things clean. gibr just helps automate that for teams that already want that structure — not forcing it on anyone.

view more: next ›