I updated my little project to also consider closed PRs in the list.
TIL: draft PRs are considered state: "open" in #GitHubCLI
I updated my little project to also consider closed PRs in the list.
TIL: draft PRs are considered state: "open" in #GitHubCLI
🔍 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
🧹 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.
I've been using the GitHub CLI for a month or so. It really fits my work flow
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/
Check out someone else's pull request using the GitHub CLI https://mikefrobbins.com/2024/04/25/check-out-someone-elses-pr-using-gh/ #GitHub #GitHubCLI
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
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
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.
yo wtf is up with @GitHub removing the clone with ssh option from their clone button?
I only see the https option or the gh cli option.