Making it a gh extension allows us to assume, that the user has already configured gh correctly, and it gives the script a lot of gh built-in features to utilize.
gh extensisons are defined by the repo following a naming convention and git extensions requires the executable to follow a naming convention - so they could actually co exist in the same repo.
Making it a gh extension allows us to assume, that the user has already configured gh correctly, and it gives the script a lot of gh built-in features to utilize.
gh extensisons are defined by the repo following a naming convention and git extensions requires the executable to follow a naming convention - so they could actually co exist in the same repo.