pyaction
cli
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
pyaction
-
generate-sitemap 1.10.0 Released
Bump cicirello/pyaction from 4.25.0 to 4.26.0
-
pyaction 4.26.0 Released
pyaction - A Docker container with Python, git, and the Github CLI
-
javadoc-cleanup 1.3.7 Released (minor bug fixes)
Bump cicirello/pyaction from 4.11.1 to 4.25.0, including upgrading Python within the Docker container to 3.12.
-
pyaction 4.23.0 Released
I just released pyaction 4.23.0, a Docker container with Python, git, and the GitHub CLI. You can pull pyaction from either the GitHub Container Registry or from Docker Hub.
-
Celebrating over 2 million pulls of pyaction from the GitHub Container Registry
A while back, I developed, and have since been maintaining, pyaction, which is a Docker container with Python, git, and the GitHub CLI. Sometime in the past week, pyaction surpassed 2 million pulls from the GitHub Container Registry.
-
pyaction: Over 1 million pulls from the GitHub Container Registry
Recently, pyaction passed 1 million pulls from the GitHub Container Registry. It is a Docker container with Python, git, and the GitHub CLI.
-
generate-sitemap 1.9.1 Released
Bump cicirello/pyaction from 4.12.0 to 4.14.1
-
pyaction 4.14.1 Released
I just released pyaction 4.14.1, a Docker container with Python, git, and the GitHub CLI.
-
pyaction: A Docker container with Python, git, and the GitHub CLI
The pyaction container is a Python slim image on top of which I've added git and the GitHub CLI, as well as gpg and curl. For the motivating usecases, I mainly need Python, git, and the GitHub CLI. The pyaction image includes gpg and curl because they are needed to install the GitHub CLI, and I saw no point in uninstalling them afterwards as part of the container build. It is available from both Docker Hub and the GitHub Container Registry.
cli
-
Tools that keep me productive
GitHub CLI - GitHub on the command line. Great for creating PRs, etc.
-
The power of the CLI with Golang and Cobra CLI
This package is widely used for powerful CLI builds, it is used for example for Kubernetes CLI and GitHub CLI, in addition to offering some cool features such as automatic completion of shell, automatic recognition of flags (the tags) , and you can use -h or -help for example, among other facilities.
-
pyaction 4.28.0 Released
This Docker image is designed to support implementing Github Actions with Python. As of version 4.0.0., it starts with the official python docker image as the base which is a Debian OS. It specifically uses python:3-slim to keep the image size down for faster loading of Github Actions that use pyaction. On top of the base, we've installed curl gpg, git, and the GitHub CLI. We added curl and gpg because they are needed to install the GitHub CLI, and they may come in handy anyway (especially curl) when implementing a GitHub Action.
-
The Ladybird Browser Project
You might be interested in GitHub's cli tool, which is open source, if you want to access GitHub without running their proprietary JS code.
https://cli.github.com/
-
Ok Boomer! Instant GitHub Repo Creation in One Command 🚀
👉 Note: This script uses the GitHub CLI. So make sure you've installed that if you haven't already. Instructions here.
-
Essential Command Line Tools for Developers
View on GitHub
-
NixOS has one fatal flaw
(Context: I'm pretty thick into Nix, and have been for about four years. Most of this post is focussed on the NixOS desktop experience, so DevOps nerds, ymmv.)
Unpopular opinion: Nix is not that hard.
What's "hard" from a nix-promotion strategy is motivating people to understand why they would want the benefits it offers. Mostly because Nix, especially with home-manager, dramatically worsens UX for several day-to-day tasks, simply by violating the Law of Least Surprise every couple of hours in normal use.
I want a fully idempotent, version-locked, rewindable user environment, with a version-controlled central config, because I have half a dozen devices that, for reasons, I need to keep perfectly interchangeable with one another. Most users do not want this, for the simple fact that mutating their configs and differentiating them locally on specific machines is not a bug, but a feature.
Even more than that, it's an expectation that most software developers share as well.
Case in point: I filed a bug against the GitHub CLI last week. If any org has the scope and motivation to build software that's compatible with NixOS, an OS most of whose users are developers, it should be GitHub, which is, at least notionally, all about developers, developers, developers. A change in GH required a config format migration, which was sensibly done by opening the config .yml and rewriting it.
Of course, this breaks NixOS not just in practice but in principle. NixOS/home-manager makes config files read-only. Surprise! https://github.com/cli/cli/issues/8462
The response from GitHub was basically, "yeah, we knew this was going to happen, we mentioned it to the packagers at NixOS, but we did it anyway, because it was still the best way to proceed for us." (And they weren't wrong.)
Now, once a month is an annoyance, but I run into these problems daily. I can't imagine any sane person -- which I am not -- would persist with using it.
Why do I keep using NixOS, then? Because I am terribly and disproprotionately annoyed by small changes in my user experience, which I find disruptive to my workflow and hence threaten my success. For me, forbidding apps from mutating the config files I established for them is a selling point. Being able to version-control an idempotent declarative config for all of them at once is heaven.
Unless you're like me, you'll hate NixOS. But some were meant for Nix.
Because
-
How do you handle secret rotation in kubernetes (i. e. with github access tokens)
To use a proper dynamic auth for ghcr.io you can create a "credential helper" and then it is supported by flux, see here: https://fluxcd.io/flux/cheatsheets/oci-artifacts/#authentication Unfortunately the "official" credential helper for ghcr.io doesn't exist. I use this simple script as a helper: https://gist.github.com/pkit/a98411d21ecc9293066f4579088187d1 Which requires gh cli to be installed.
-
pyaction 4.27.0 Released
This Docker image is designed to support implementing Github Actions with Python. As of version 4.0.0., it starts with the official python docker image as the base which is a Debian OS. It specifically uses python:3-slim to keep the image size down for faster loading of Github Actions that use pyaction. On top of the base, we've installed curl gpg, git, and the GitHub CLI. We added curl and gpg because they are needed to install the GitHub CLI, and they may come in handy anyway (especially curl) when implementing a GitHub Action.
-
Everything I install and set up on a new MacBook as a web developer
Two CLI tools I install right away are the GitHub CLI (via brew) and the Netlify CLI (via npm).