ytreister
ytreister on Hacker News
I do not mind the Git CLI, and I just carry around my alises. I also built a tool to make it even more powerful and integrate with issue trackers:
https://pypi.org/project/gibr/
I implemented this in version 0.6.0 which was just released.
https://github.com/ytreister/gibr/releases/tag/0.6.0
The issue assignee can be used in the branch name.
In the future I want to allow a user to easily assign an issue to the current user if they use gibr with an unassigned issue
I understand, but that means you need to review the commits and code changes and do not have the context which could be found either in the issue title, description, etc.
OK, so it is possible that when the gibr pr command gets added that it could be helpful. My thought is for it to automate the creation of the PR and will contain the description which links to the Jira issue.
I have not gotten there yet though
Interesting idea, however, don't you first need to create the branch before you start committing commits?
I am not sure how configurable the button in Linear is. Also, gibr allows a user to not need to even leave their terminal to list their issues and create/push the branch. I also hope to have more features like creating a PR/MR and linking to a git repo.
Also many people do not have the luxury of using Linear, many companies force developers to use Jira...
Interesting. That seems to work if your work is not associated with an issue tracker. Many use issue trackers and like to link each branch or PR/MR to an issue tracker.
I don't know why I did not think of that, but I can see how people would assume this nowadays!
Why would you do this!!!!!
Exactly, people tend to leave messes. It makes it much easier to know what the branch was for and have more piece of mind when you want to delete it.
gibr makes it super easy to do exactly this!
gibr makes it easy to do this and in a consistent manner
That is what gibr does, it helps you do this with ease
Hey everyone — I’m actually the author of gibr!
I just wanted to say thanks for all the comments and discussion. It’s been amazing (and honestly a bit surprising) to see so many developers checking it out.
The idea for gibr came from the frustration I had when I was forced to use Jira for issue tracking and GitLab for our repos. At the time, I built an internal tool called jig that integrated the two. With a single command, it could create a branch, push it, transition the Jira issue to In Progress, and open a merge request with everything pre-filled — assignee, reviewers, description, and so on. It became really popular at my company.
I decided to take that idea further and rebuild it as an open-source tool with a plugin architecture, so it could work with any issue tracker or Git provider, not just Jira and GitLab.
If anyone has feedback or ideas for new integrations, I’d love to hear them — some great suggestions have already come in that might make it into the next release.
Thanks again for the support — this community is awesome.
Yes, I agree, and that is why I created this tool
When you use Gitlab and squash your merge request, a new merge commit with the name of the branch is created, so I found it very helpful in that situation to know the name of the branch.
I used some AI to help me, but I put in a lot of thought to how it is created. I have plans to add many more useful features over time.