alias-tips VS starter-workflows

# Set ZSH_CUSTOM if it's not already (used by our PLUGINS_PATH below) if [ -z $ZSH_CUSTOM ]; then ZSH_CUSTOM="$HOME/.oh-my-zsh/custom" fi # Install additional plugins to this path PLUGINS_PATH="${ZSH_CUSTOM}/plugins" # Define function for installing plugins for use below function install-plugin() { plugin_repo=$1 plugin_name=$2 echo "Downloading Plugin: $plugin_name" echo "Using: $plugin_repo" echo "To: $PLUGINS_PATH/$plugin_name" echo "git clone $plugin_repo $PLUGINS_PATH/$plugin_name" git clone $plugin_repo $PLUGINS_PATH/$plugin_name plugin_list="${plugin_list}$plugin_name " } echo "Installing Plugins..." install-plugin https://github.com/djui/alias-tips alias-tips install-plugin https://github.com/wting/autojump autojump install-plugin https://github.com/TamCore/autoupdate-oh-my-zsh-plugins autoupdate install-plugin https://github.com/zsh-users/zsh-autosuggestions autosuggestions echo "Plugins Installed. Add them by copying th following into your ~/.zshrc plugins=( $plugin_list ) " # For auto jump we must install it using it's own script cd "$PLUGINS_PATH/autojump" ./install.py

There’s a zsh plugin for that: https://github.com/djui/alias-tips

https://github.com/djui/alias-tips this is different but I found it quite useful, it will give you shorter version of commands if you have aliases matched the current commands

The best plugin that I've seen recently is alias-tips, which if you run the command and you've got an alias configured for that, it pops up and says, "Hey, don't forget you can type this." So if I'm using Kubernetes and I write Kubectl, apply -f and then the manifest path, it'll say, "Hey, don't forget you can just run K-A-F, and then the path." So that's probably the best plugin that I've seen recently.

alias-tips 🥇 - An oh-my-zsh plugin to help remembering those aliases you defined once.

👉 Install alias-tips

GitHub, as one of the leading web-based Git repository hosting service, provides a powerful suite of CI/CD tools in the form of GitHub Actions. These are directly integrated into the platform which empowers developers to increase the speed, efficiency and reliability of delivering products. In this brief article, we will take a look at what CI/CD is, why we should use it, as well as some of its applications in my projects.

GitHub Actions is a modern CI/CD tool integrated natively on GitHub. Itenables the rapid automation of build, test, deployment, and other custom workflows on GitHub with no need for external tools.

GitHub Actions is GitHub's CI/CD solution. You can use it to run automated tasks each time you change your code. Although the platform lacks a built-in Kubernetes integration, third-party plugins such as Azure's Deploy to Kubernetes Cluster action can automate deployments and manage different rollout strategies.

GitHub Actions is a feature-rich CI/CD platform embedded within GitHub, enabling developers to automate, customize, and execute software development workflows directly in their repositories. An Action inside GitHub Actions is a discrete unit of automation that performs a specific task within a workflow. All the Actions are reusable, and there are many to choose from. You can even create your own reusable ones.

actions/starter-workflows

The real power of using PHP code-quality tools is when it’s added to your continuous integration process, which means it automatically checks the code every time someone makes a push or pull request to your project repo. In this section, we'll be looking at how to do just that. GitHub actions is available for free so we'll use it for demo purposes. Note that there are some limits to private repos, so set your test repo to public if you can.

You can even automate the running of this script — hence the directory name automation — to happen every time the data changes, using GitHub Actions.

# Based on https://github.com/actions/starter-workflows/blob/main/ci/node.js.yml name: CI on: pull_request: branches: - main jobs: ci: runs-on: ubuntu-latest steps: - uses: actions/checkout@v2 - uses: actions/setup-node@v2 with: node-version: lts/* cache: 'npm' - run: npm ci - run: npm run build --if-present - run: npm test

You might remember that I’ve been taking an interest in GitHub Actions for the last year or so (I even wrote a book on the subject). And at the Perl Conference in Toronto last summer I gave a talk called “GitHub Actions for Perl Development” (here are the slides and the video).