You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Even if it's in a separate GitHub repository, I think a gh CLI extension is a good idea. It'd be cool to have a CLI tool in addition to the web tool that's listed in the readme. It'd be even cooler if it were "official" as in same owner (alexharatarakis or organization; though I see an organization got shot down pretty hard in #171 ) or even same repo (monorepo or something)
Users could use my extension and use -source alexkaratarakis/gitattributes, or gh config set gh_gitattributes_source alexkaratarakis/gitattributes for something more permanent.
Or you could just fork my repo and change the default 😉
@spenserblack seems to have a vastly better solution than my very crude one. 😱 I think that this project could link to that project in the readme or something?
Even if it's in a separate GitHub repository, I think a
gh
CLI extension is a good idea. It'd be cool to have a CLI tool in addition to the web tool that's listed in the readme. It'd be even cooler if it were "official" as in same owner (alexharatarakis or organization; though I see an organization got shot down pretty hard in #171 ) or even same repo (monorepo or something)I know @spenserblack had this idea for their gitattributes collection spenserblack/.gitattributes#2 and I think that same idea is good one for this collection too.
I've got the beginnings of one here https://github.com/jcbhmr/gh-gitattributes (it uses Bash lmao not even Go like https://github.com/garnertb/gh-gitignore)Just thought I'd bring this up.
The text was updated successfully, but these errors were encountered: