11–20 of 82 posts
You may want to review https://www.git-scm.com/about/trademark They have been stingy about projects with git in the name.
Have they? GitKraken & GitLens are pretty popular, commercial offerings, and they have been on the market for years. [0] https://www.gitkraken.com
You may want to review https://www.git-scm.com/about/trademark They have been stingy about projects with git in the name.
You may want to review https://www.git-scm.com/about/trademark They have been stingy about projects with git in the name.
It's Git's own convention to add subcommands by placing a binary on the $PATH with the prefix `git-`. In this case, the subcommands becomes `git bug ...`.
How would one name this differently?
I tend to think this is more about commercial projects.
Wow, I've wanted this for ages and always thought it would be possible. Interesting to integrate it with things like version tags for tracking releases and things like bugs fixed and known problems in a release document.
Hi, author here. Happy to answer questions. Version 0.8 just got out[1]. For the next one, I'll try to focus on making the codebase fully ready for multi-entities and introduce a Project Board. Later we can add support for code review! If you are looking for how it works, you can have a look at the data model introduction[2]. git-bug is only pushed forward by volunteers so it's taking its time to fully grow, so I'll…
Hi, author here. Happy to answer questions. Version 0.8 just got out[1]. For the next one, I'll try to focus on making the codebase fully ready for multi-entities and introduce a Project Board. Later we can add support for code review! If you are looking for how it works, you can have a look at the data model introduction[2]. git-bug is only pushed forward by volunteers so it's taking its time to fully grow, so I'll…
"Keep reading and writing bugs " sounds a little off. Maybe change that to "writing bug reports"?
Earlier quoted context omitted.
"Keep reading and writing bugs " sounds a little off. Maybe change that to "writing bug reports"?
Strong disagree. "Keep writing bugs" makes OP sound experienced, self-deprecating, and not self-serious. These are good things.
Earlier quoted context omitted.
"Keep reading and writing bugs " sounds a little off. Maybe change that to "writing bug reports"?
Strong disagree. "Keep writing bugs" makes OP sound experienced, self-deprecating, and not self-serious. These are good things.