Viewing profile — ytreister
ytreister
HN member- Joined
- Sat, Nov 01, 2025, 6:03 PM UTC
- HN karma
- 6
- Public activity
- 21 items
- HN profile
- View on Hacker News ↗
About ytreister
No profile information was provided.
Recent public activity
-
comment
Comment #45885855
I tried it with my repo and it is actually really nice. I kind of want to link to this so that anyone wanting to make contributions to my repo can learn about the code structure. M…
-
comment
Comment #45885700
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/
-
comment
Comment #45796749
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…
-
comment
Comment #45796744
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.
-
comment
Comment #45788511
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.
-
comment
Comment #45788492
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 wh…
-
comment
Comment #45784542
Interesting idea, however, don't you first need to create the branch before you start committing commits?
-
comment
Comment #45784523
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 ho…
-
comment
Comment #45784499
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.
-
comment
Comment #45784487
Unfortunately, gibr does not yet support username in the branch name, but I created an issue and hopefully can get it done very soon https://github.com/ytreister/gibr/issues/42
-
comment
Comment #45784482
I don't know why I did not think of that, but I can see how people would assume this nowadays!
-
comment
Comment #45784390
Why would you do this!!!!!
-
comment
Comment #45784386
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.
-
comment
Comment #45784353
I added a new TODO issue so that username can be configured in the branch name. gibr currently does not have support for username. https://github.com/ytreister/gibr/issues/42
-
comment
Comment #45784322
gibr makes it super easy to do exactly this!
-
comment
Comment #45784316
gibr makes it easy to do this and in a consistent manner
-
comment
Comment #45784312
That is what gibr does, it helps you do this with ease
-
comment
Comment #45784108
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 de…
-
comment
Comment #45784018
Yes, I agree, and that is why I created this tool
-
comment
Comment #45783989
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 b…
-
comment
Comment #45783931
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.