take-action
cli
take-action | cli | |
---|---|---|
5 | 254 | |
50 | 35,528 | |
- | 1.2% | |
2.7 | 9.7 | |
about 1 month ago | 6 days ago | |
Go | ||
MIT License | MIT License |
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.
take-action
-
GitHub Actions: A Maintainer's Best Friend
My coworker bdougie (@bdougieyo) created the take Github action. It allows external contributors to self-assign issues by typing .take into a comment of an issue. This removes the burden of a bit of back and forth between contributors and maintainers.
-
How to Edit a Github Action
You can find my PR here. In this PR, I made a pull request comparing my branch to the author’s branch.
-
Build your own GitHub Action WITHOUT a Docker Container
I recently moved my bdougie/take-action to run out of the yml and not look back. Here is that PR.
-
Build GitHub Actions with a Docker Container
And now you can push this to GitHub to test it from a repo. I leverage this actual action in my repo bdougie/take-action got a response back from my action, it looks like it worked okay.
-
Assigning new contributors to issues using GitHub Actions
bdougie / take-action
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).
What are some alternatives?
github-script - Write workflows scripting the GitHub API in JavaScript
cobra - A Commander for modern Go CLI interactions
redux-ecosystem-links - A categorized list of Redux-related addons, libraries, and utilities
gh.vim - Vim/Neovim plugin for GitHub
app - 🍕 Insights into your entire open source ecosystem.
glab - The GitLab CLI tool. Archived: now officially adopted by GitLab as the official CLI tool and maintained at https://gitlab.com/gitlab-org/cli. See https://github.com/profclems/glab/issues/983
naming-cheatsheet - Comprehensive language-agnostic guidelines on variables naming. Home of the A/HC/LC pattern.
vscode-dev-containers - NOTE: Most of the contents of this repository have been migrated to the new devcontainers GitHub org (https://github.com/devcontainers). See https://github.com/devcontainers/template-starter and https://github.com/devcontainers/feature-starter for information on creating your own!
nissuer - A GitHub Action for tried and tired maintainers.
octo.nvim - Edit and review GitHub issues and pull requests from the comfort of your favorite editor
deploy-with-actions
cockroach - CockroachDB - the open source, cloud-native distributed SQL database.