Andy Feller

Thanks for raising this issue, @ilmanzo! 🙇 I'm going to defer this to our Packages Security maintainers for follow up. cc: @cli/package-security

> Given I do not have the workflow scope for my token > And Given the release I'm creating requires it (and therefore returns a 404) > When I run...

@PaulFWatts : **Could you provide a little more information about the problem you're running into given `gh-copilot` [already provides `windows-amd64` distribution](https://github.com/github/gh-copilot/releases/tag/v1.0.5)?** 

@mntlty : thank you for sussing out room for improvement! ❤ I suspect any command that has flags for assignees could be impacted by including `@` for logins beyond `@me`...

> A little while back the import path of github.com/alessio/shellescape changed to al.essio.dev/pkg/shellescape . This PR handles that, so people can update again. **Could you explain the benefits and tradeoffs...

> I think this is best raised to the upstream as we have no influence how the upstream module is defined. > > My understanding is that without this change...

Thank you for taking the time to raise this concern as well as sharing your workaround, @BrianL-STCU! ❤ I'd like to ask a few questions to understand the potential scope...

Appreciate ideas for making it easier for extension authors to build better tests, a sentiment I believe @williammartin and I both support! ❤ I'm hesitant putting `localhost`/`127.0.0.1` specific logic into...

**@gberche-orange : could you share how you are using the custom properties as part of your overall `gh` workflow?** Beyond setting the value of a custom property for a given...

## How might these new commands look within `gh`? ### Ideating ```shell # Spreading custom properties across multiple commands using long name... gh org custom-property list gh org custom-property view...