Things I wished were packaged in #Fedora are #wezTerm the #HelixEditor the #awscliv2 and the #GitHubCLI

Now sports both `lint` and `view` commands, though no auto-fix yet. There's a few scenarios I hadn't considered with how my team uses it I need to rethink how to automatically solve while keeping a generic clean-up possible as well.

#GitHubCLI #golang

Maintaining a #monorepo already has enough challenges. Keeping its #CODEOWNERS up to date can be difficult. I started on a new #GitHubCLI extension: `gh ext install heaths/gh-codeowners`

It does only simple linting for now but will have a fix mode for supported error types.

See https://github.com/heaths/gh-codeowners/releases/tag/v0.1.0 for more information. #GitHub

Nothing like writing a #GitHubCLI extension to work around a bug in the CLI for which I've had a PR out for over 9 months waiting for one person to review it (other staffers have already), but here we are: https://github.com/heaths/gh-merge-json

`gh api --paginate` may return invalid JSON, so this extension does what my PR does but within the gh ecosystem.

Just `gh ext install heaths/gh-merge-json` and pipe paginated JSON to it to merge the JSON (mainly nested arrays) and get back valid JSON.

#GitHub

Why use #GitHubCLI at all if you can't do commits or pushes with it? :blobfoxangrylaugh:

@roguequery if you're interested in making this template...we'll, more template-like so people can just define a few replacement variables...check out https://github.com/heaths/gh-template. It's a #GitHubCLI extension to "fork" the template and uses #golang templates for replacement.

Like you, I also got tired of copypasta but also all manual replacements.

@drsensor raise an issue?

https://github.com/cli/cli

Double-check on a different machine (e.g. a VM) and upgrade to the latest version before you do, just in case, and give as much info as you can about what's going wrong.

#GitHubCLI

@robpomeroy and if people would like an example using #golang, check out my #GitHubCLI extension: https://github.com/heaths/gh-projects, specifically the files under internal/cmd.

#GraphQL may seem daunting at first, but you only get what data you asked for and can effectively combine multiple requests in a single fetch.

Note: may not be the most optimized requests, but is geared for infrequent access.

Now if only #GitHub would fill out all the missing functionally for Projects V2 you find in V1.

Use the #GitHubCLI to run `gh api --paginate` and tired of having to rely on installing external tools or otherwise munge invalid concatenated JSON from all responses? Consider upvoting https://github.com/cli/cli/pull/5652 to hopefully finally get this PR merged that fixes the problem. #GitHub #golang

Only org-level secrets on GitHub can be shared with other repositories in the same org. AFAIK personal profile repositories need to create actions secrets on each repo.

How do I now set #github actions @jreleaser secrets for a new non-org repo?

`gh secret set -f ~/.jreleaser/config.properties`

🚀 All necessary secrets are created on remote repo!

#GitHubCLI

@mmeier If it helps, for setting up one-off projects I made a #GitHubCLI extension that may help: https://github.com/heaths/gh-template #golang

gh extension install heaths/gh-template
gh template clone heaths/template-golang

You can also make your own template repos.

Published another new version of my #GitHubCLI extension https://github.com/heaths/gh-template to clone and format template repos, now that optionally clones labels*, supports boolean expressions to condition blocks of templates, and allows for different template delimiters. #golang #github

(*One of several features I've added to the CLI itself. The extension now does it automatically with --labels when you clone.)

I released a new version of my #GitHubCLI extension gh-template which can clone and format a repository template in a single command and re-prompt the user for some parameter types: https://github.com/heaths/gh-template #golang #GitHub

Updated a couple of my own template repositories to take advantage of the github.com/heaths/gh-template #GitHubCLI extension:

https://github.com/heaths/template-golang #golang

https://github.com/heaths/template-rustlang #rustlang

Can use falsy conditional in README to give instructions and have it templated out:

Just published the first version of a new #GitHubCLI extension to format a project template after cloning from a repo template: https://github.com/heaths/gh-template

It adds some built-in parameters based on the #GitHub repo and you can pass or prompt for additional parameters.

gh repo create <name> --template <template> --clone
cd <name>
gh template apply

More improvements yet to come, but this marks the MVP. Issues and suggestions welcome! #golang

@Parkplusplus @savannah I've contributed a lot to the #GitHubCLI itself, though I've had several PRs go completely ignored for months after maintainers gave an initial thumbs up but also feedback. Really irritating. Lately I've been focusing more on extensions.

There's a bunch of scripts checked into our repos that utilize the extension, like being able to add issues across language repos.

Now that #GitHub added the ability to link a project V2 to a repo, I've made an update to my heaths/gh-projects #GitHubCLI extension: https://github.com/heaths/gh-projects #golang

Org or user projects (V2) will be automatically linked to a repository if necessary, obviating the need to manually link them. Now you can add issues and set fields with less hassle.

Hopefully they'll be adding new caps soon to clone projects or views. rounding out most of what we need for managing #AzureSDK cross-language issues.