ytreister

5 ms·

1.
by ytreister 11mo ago
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. My repo has a plugin structure ( https://github.co
2.
by ytreister 11mo ago
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/
3.
by ytreister 11mo ago
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 t
4.
by ytreister 11mo ago
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.
5.
by ytreister 11mo ago
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.
6.
by ytreister 11mo ago
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 tho
7.
by ytreister 11mo ago
Interesting idea, however, don't you first need to create the branch before you start committing commits?
8.
by ytreister 11mo ago
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 a
9.
by ytreister 11mo ago
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.
10.
by ytreister 11mo ago
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
11.
by ytreister 11mo ago
I don't know why I did not think of that, but I can see how people would assume this nowadays!
12.
by ytreister 11mo ago
Why would you do this!!!!!
13.
by ytreister 11mo ago
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.
14.
by ytreister 11mo ago
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
15.
by ytreister 11mo ago
gibr makes it super easy to do exactly this!
16.
by ytreister 11mo ago
gibr makes it easy to do this and in a consistent manner
17.
by ytreister 11mo ago
That is what gibr does, it helps you do this with ease
18.
by ytreister 11mo ago
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 fr
19.
by ytreister 11mo ago
Yes, I agree, and that is why I created this tool
20.
by ytreister 11mo ago
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.
21.
by ytreister 11mo ago
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.