#githubcli — Public Fediverse posts
Live and recent posts from across the Fediverse tagged #githubcli, aggregated by home.social.
-
Be careful running trusted or untrusted code with access to your environment variables.
If you're using the #GitHubCLI or #CopilotCLI on a personal computer, sensitive variables may be exposed:
- `GH_TOKEN`
- `GH_ENTERPRISE_TOKEN`
- `GITHUB_TOKEN`
- `GITHUB_ENTERPRISE_TOKEN`
- `GITHUB_AUTH_TOKEN`These can be read by any executed process, and in some cases tools may also expose tokens via commands like:
`gh auth token`
Treat your environment as compromised when executing code.
-
via @dotnet : Modernize .NET Anywhere with GitHub Copilot
https://ift.tt/5x4R9PK
#dotnet #NET #GitHubCopilot #Copilot #modernize-dotnet #modernize # modernization #VSCode #VisualStudio #GitHubCLI #CLI #codingagents #customskills #developerexperience #softwaredev… -
via @dotnet : Modernize .NET Anywhere with GitHub Copilot
https://ift.tt/5x4R9PK
#dotnet #NET #GitHubCopilot #Copilot #modernize-dotnet #modernize # modernization #VSCode #VisualStudio #GitHubCLI #CLI #codingagents #customskills #developerexperience #softwaredev… -
via @dotnet : Modernize .NET Anywhere with GitHub Copilot
https://ift.tt/5x4R9PK
#dotnet #NET #GitHubCopilot #Copilot #modernize-dotnet #modernize # modernization #VSCode #VisualStudio #GitHubCLI #CLI #codingagents #customskills #developerexperience #softwaredev… -
via @dotnet : Modernize .NET Anywhere with GitHub Copilot
https://ift.tt/5x4R9PK
#dotnet #NET #GitHubCopilot #Copilot #modernize-dotnet #modernize # modernization #VSCode #VisualStudio #GitHubCLI #CLI #codingagents #customskills #developerexperience #softwaredev… -
via @dotnet : Modernize .NET Anywhere with GitHub Copilot
https://ift.tt/5x4R9PK
#dotnet #NET #GitHubCopilot #Copilot #modernize-dotnet #modernize # modernization #VSCode #VisualStudio #GitHubCLI #CLI #codingagents #customskills #developerexperience #softwaredev… -
🔍 I built a new thing: gh-find!
A find(1)-like utility for searching files across GitHub repositories from the command line.
• Intuitive glob patterns (**/*.go, *.test.js)
• Search branches, tags, or commits (owner/repo@ref)
• Filter by type, extension, size, or date
• Concurrent search with automatic caching
• Integrates with GitHub CLI -
Dew Drop – September 29, 2025 (#4507)
https://fed.brid.gy/r/https://alvinashcraft.com/2025/09/29/dew-drop-september-29-2025-4507/
-
🧹 Tidying Up After Myself: Automatically Deleting Old GitHub Issues
At some point, I had to admit it: I’ve turned GitHub Issues into a glorified chart gallery. Let me explain. Over on my amedee/ansible-servers repository, I have a workflow called workflow-metrics.yml, which runs after every pipeline. It uses yykamei/github-workflows-metrics to generate beautiful charts that show how long my CI pipeline takes to run. Those charts are then posted into a GitHub Issue—one per run. It’s neat. It's visual. It's entirely unnecessary to keep them […]https://amedee.be/%f0%9f%a7%b9-tidying-up-after-myself-automatically-deleting-old-github-issues/
-
🧹 Tidying Up After Myself: Automatically Deleting Old GitHub Issues
At some point, I had to admit it: I’ve turned GitHub Issues into a glorified chart gallery. Let me explain. Over on my amedee/ansible-servers repository, I have a workflow called workflow-metrics.yml, which runs after every pipeline. It uses yykamei/github-workflows-metrics to generate beautiful charts that show how long my CI pipeline takes to run. Those charts are then posted into a GitHub Issue—one per run. It’s neat. It's visual. It's entirely unnecessary to keep them […]https://amedee.be/%f0%9f%a7%b9-tidying-up-after-myself-automatically-deleting-old-github-issues/
-
🧹 Tidying Up After Myself: Automatically Deleting Old GitHub Issues
At some point, I had to admit it: I’ve turned GitHub Issues into a glorified chart gallery. Let me explain. Over on my amedee/ansible-servers repository, I have a workflow called workflow-metrics.yml, which runs after every pipeline. It uses yykamei/github-workflows-metrics to generate beautiful charts that show how long my CI pipeline takes to run. Those charts are then posted into a GitHub Issue—one per run. It’s neat. It's visual. It's entirely unnecessary to keep them […]https://amedee.be/%f0%9f%a7%b9-tidying-up-after-myself-automatically-deleting-old-github-issues/
-
🧹 Tidying Up After Myself: Automatically Deleting Old GitHub Issues
At some point, I had to admit it: I’ve turned GitHub Issues into a glorified chart gallery. Let me explain. Over on my amedee/ansible-servers repository, I have a workflow called workflow-metrics.yml, which runs after every pipeline. It uses yykamei/github-workflows-metrics to generate beautiful charts that show how long my CI pipeline takes to run. Those charts are then posted into a GitHub Issue—one per run. It’s neat. It's visual. It's entirely unnecessary to keep them […]https://amedee.be/%f0%9f%a7%b9-tidying-up-after-myself-automatically-deleting-old-github-issues/
-
🧹 Tidying Up After Myself: Automatically Deleting Old GitHub Issues
At some point, I had to admit it: I’ve turned GitHub Issues into a glorified chart gallery. Let me explain. Over on my amedee/ansible-servers repository, I have a workflow called workflow-metrics.yml, which runs after every pipeline. It uses yykamei/github-workflows-metrics to generate beautiful charts that show how long my CI pipeline takes to run. Those charts are then posted into a GitHub Issue—one per run. It’s neat. It's visual. It's entirely unnecessary to keep them […]https://amedee.be/%f0%9f%a7%b9-tidying-up-after-myself-automatically-deleting-old-github-issues/
-
Grab it while it‘s hot! Release v2.1.0 of gh-get is available for download. gh-get streamlines the process of cloning GitHub repositories by putting them into a conventional directory structure. Run gh get jane-doe/awesome-repo and it will clone that repo into ~/github/jane-doe/awesome-repo. Never search around for the place you cloned that repo to.
Install it via gh extension install britter/gh-get. https://github.com/britter/gh-get
#GitHub #GitHubCLI #git #release -
So I did a thing today. I finally took some time to rewrite the GitHub CLI extension gh-get in Go. It’s an extension that clones repositories and puts them into a standardized directory layout like so: ~/github/<owner>/<repository>
No more „did I clone this before?“ or „where did I clone this to?“ it’s inspired by the ghq CLI tool. https://github.com/britter/gh-get
#GitHub #GitHubExtension #GitHubCLI #GoLang #git -
I added support to the #GitHubCLI to “search” gists - well, filter, technically, since there are no APIs to search gists. Also adds a new view when including gists’ content in the search much like code search.
Download https://github.com/cli/cli/releases/latest and run `gh gist list —help` for more information.
-
Updated my #GitHubCLI extension to view information about CODEOWNERS: https://github.com/heaths/gh-codeowners
Added a new `pr` command to view all a PR's files' owners e.g., `gh code owners pr #123`
Nice to jump back into a little #golang
-
Boost your CLI skills with GitHub Copilot.
#githubcopilot #githubcli #git #cli #commandline #ai #learning
https://github.blog/developer-skills/programming-languages-and-frameworks/boost-your-cli-skills-with-github-copilot/ -
My latest post about the GitHub CLI is out! Maybe you'll find it helpful. https://dev.to/opensauced/boost-productivity-with-the-github-cli-2mne #github #githubcli
-
What if we could script the creation and configuration of a GitHub Repository so that it is ready to provision or deploy Azure resources from a GitHub Actions pipeline?
That's the topic of my new article that uses GitHub CLI and Azure CLI to script the GitHub repository 👉 https://drp.li/42tSe
🔒 Authentication to Azure is done using workload federation identity / Open ID Connect.
-
I have been playing with the GitHub CLI and I love it. A bit disappointed though that you can't change the output of all commands to json to take profit of the jq flag. They should have taken inspiration from Azure CLI that does it right #GitHubCLI #github #azurecli
-
I've been waiting for someone else to write this package for a while! https://omnivore.app/scrap1893/https-www-armindarvish-com-en-post-consult-gh-working-with-githu-18adecc433f #emacs #github #GitHubCLI
-
I just discovered Github's command line tool... with some minimal configuration you can save time via the command line... and enjoy many extensions contributed by the community... Want to take a look? I've prepared a simple recipe. Enjoy it!
#cvs #scv #git #versioncontrol #controldeversiones #github
#githubuniverse #coding #floss #opensource #commandline #Prompt #terminal #Linux #linuxuser #gistlover #gist #recipe #snippets #snippet #codelife #code #githubCLI #community
https://gist.github.com/davidjguru/f1726fd8e384693c77279ac832e3e01e -
I just discovered Github's command line tool... with some minimal configuration you can save time via the command line... and enjoy many extensions contributed by the community... Want to take a look? I've prepared a simple recipe. Enjoy it!
#cvs #scv #git #versioncontrol #controldeversiones #github
#githubuniverse #coding #floss #opensource #commandline #Prompt #terminal #Linux #linuxuser #gistlover #gist #recipe #snippets #snippet #codelife #code #githubCLI #community
https://gist.github.com/davidjguru/f1726fd8e384693c77279ac832e3e01e -
I just discovered Github's command line tool... with some minimal configuration you can save time via the command line... and enjoy many extensions contributed by the community... Want to take a look? I've prepared a simple recipe. Enjoy it!
#cvs #scv #git #versioncontrol #controldeversiones #github
#githubuniverse #coding #floss #opensource #commandline #Prompt #terminal #Linux #linuxuser #gistlover #gist #recipe #snippets #snippet #codelife #code #githubCLI #community
https://gist.github.com/davidjguru/f1726fd8e384693c77279ac832e3e01e -
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.
-
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
-
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
-
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
-
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
-
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.
-
@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?
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.
-
@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
-
@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-golangYou 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: