Andy Feller

> If I publish an GitHub CLI extension, I would expect the GitHub CLI README or GitHub.com documentation to outline license responsibilities/requirements. There is a lot more in this sentence...

> I wanted to add an example of a project that shows dependency license information in a nice way: https://github.com/neutralinojs/neutralinojs?tab=readme-ov-file#licenses-and-copyrights Really appreciate that, @ataylorme! Also, we Andrews have to look...

> > readily provide this information to users at the drop of the hat through something like gh licenses. > > Oh man, that and the [gh license extension](https://github.com/mislav/gh-license) would...

Thanks for writing this up! ❤ Curious, I think your theory has a bit of merit as this code path goes through [`api.HandleHTTPError()` in `cli/go-gh`](https://github.com/cli/go-gh/blob/25db6b99518c88e03f71dbe9e58397c4cfb62caf/pkg/api/errors.go#L100-L154) which doesn't appear to preserve...

@roryabraham : That is definitely a lot of time spent in CI each and every time! > _"only fetch the commit history of the given pull request, and not more"_...

> 3\. However, I can confirm that adding a port in the YAML would keep it valid (at least as far as the ruby parser goes): > ```shell > irb(main):005>...

@fregante : Thanks for opening up this suggestion! Couple of questions to help understand the scope of this potential enhancement: 1. Would this new flag resolve this tag against the...

> Just adding a paper trail that I mentioned this idea in [#9240 (comment)](https://github.com/cli/cli/pull/9240#discussion_r1654720174) @williammartin : Thanks for the paper trail! > > However, the caveat with this "scope reduction"...

@spinningarrow : thank you for opening up this issue and my apologies for the trouble caused! 🙇 **Do you know that `gh secret set` has `-v,--visibility` flag that defaults to...

> that's quite hard to use in this scenario. I will admit it raises the question of why this endpoint was designed this way rather than allowing users to update...