Ansible Lint Action: Community Maintained Ansible-lint Github Action

Ansible Lint for GitHub Action

This action allows you to run ansible-lint on your codebase without having to install it yourself.

Usage

To use the action simply create an ansible-lint.yml (or choose custom *.yml name) in the .github/workflows/ directory.

For example:

name: Ansible Lint # feel free to pick your own name
on: [push, pull_request]

jobs:
  build:
    runs-on: ubuntu-latest

    steps:
      # Important: This sets up your GITHUB_WORKSPACE environment variable
      - uses: actions/checkout@v2

      - name: Run ansible-lint
        # replace `main` with any valid ref, or tags like `v6`
        uses: ansible-community/ansible-lint-action@main
        # optional:
        # with:
        #   path: "playbooks/"  # <-- only one value is allowed

Due to limitation on how GitHub Actions are processing arguments, we do not plan to provide extra options. You will have to make use of ansible-lint own configuration file for altering its behavior.

If you still want custom arguments, you can still fork the action and modify its action.yml file.

TIP: N.B. Use ansible/ansible-lint-action@v6 or any other valid tag, or branch, or commit SHA to pin the action to use a specific version.

Alternatively, you can run the ansible lint only on certain branches:

on:
  push:
    branches:
      - stable
      - release/v*

or on various events

License

The Dockerfile and associated scripts and documentation in this project are released under the MIT.

Credits

The initial GitHub action has been created by Stefan Stölzle at stoe/actions.

---

Download Details:

Author: ansible
Source Code: https://github.com/ansible/ansible-lint-action

License: MIT license

#github #github 

What is GEEK

Buddha Community

Ansible Lint Action: Community Maintained Ansible-lint Github Action

Ansible Lint for GitHub Action

This action allows you to run ansible-lint on your codebase without having to install it yourself.

Usage

To use the action simply create an ansible-lint.yml (or choose custom *.yml name) in the .github/workflows/ directory.

For example:

name: Ansible Lint # feel free to pick your own name
on: [push, pull_request]

jobs:
  build:
    runs-on: ubuntu-latest

    steps:
      # Important: This sets up your GITHUB_WORKSPACE environment variable
      - uses: actions/checkout@v2

      - name: Run ansible-lint
        # replace `main` with any valid ref, or tags like `v6`
        uses: ansible-community/ansible-lint-action@main
        # optional:
        # with:
        #   path: "playbooks/"  # <-- only one value is allowed

Due to limitation on how GitHub Actions are processing arguments, we do not plan to provide extra options. You will have to make use of ansible-lint own configuration file for altering its behavior.

If you still want custom arguments, you can still fork the action and modify its action.yml file.

TIP: N.B. Use ansible/ansible-lint-action@v6 or any other valid tag, or branch, or commit SHA to pin the action to use a specific version.

Alternatively, you can run the ansible lint only on certain branches:

on:
  push:
    branches:
      - stable
      - release/v*

or on various events

License

The Dockerfile and associated scripts and documentation in this project are released under the MIT.

Credits

The initial GitHub action has been created by Stefan Stölzle at stoe/actions.

---

Download Details:

Author: ansible
Source Code: https://github.com/ansible/ansible-lint-action

License: MIT license

#github #github 

GitHub Action Hero: Swechhya Bista

GitHub Actions gives you the power to automate your workflow. Connect with the tools you know and love. Have more freedom to innovate and be creative. Deploy to any cloud, build containers, automate messages, and lots more. It’s time to take control.

There’s lots of amazing Actions being built every day. We spoke to some of the coolest developers building the latest workflows and automations. Last week, we shared Samson’s story. This week we have Swechhya Bista. She also participated in our recent GitHub Actions Hackathon. Read her story for inspiration, lessons, and why developers choose to build.

#community #marketplace #open source #actions #github actions #r-action #swechhya bista

How to Create a Custom GitHub Actions Using JavaScript — Beginner Level

In this blog, we are going to learn how to create our own custom GitHub action using javaScript.

Prerequisite

• Basic JavaScript Knowledge
• Basic Git & GitHub Knowledge

About GitHub Actions

Automate, customize, and execute your software development workflows right in your repository with GitHub Actions. You can discover, create, and share actions to perform any job you’d like, including CI/CD, and combine actions in a completely customized workflow.

Types of Actions

There are three types of actions: Docker container actions, JavaScript actions, and composite run steps actions.

JavaScript Custom Action

Let’s create a Custom GitHub Action using JavaScript by creating a public repo, once the repo is created, we can clone it to our local machine using VS Code or GitPod. You need to have Node.js 12.x or higher and npm installed on your machine to perform the steps described here. You can verify the node and npm versions with the following commands in a VS Code or GitPod terminal.

node --version 
npm --version

#github #github-tutorial #github-actions #github-trend

GitHub Action Hero: Victoria Drake - The GitHub Blog

GitHub Actions allows you to automate your workflow. With GitHub Actions, you can deploy to any cloud, build containers, automate messages, and do so much more. Use any tool you know and love, and have more freedom to innovate and be creative. It’s time to take control!

Everyday, there are lots of amazing Actions being built. We spoke to some of the coolest developers building the latest Actions. Over the next few weeks we’ll be sharing their stories with lots of tips to inspire you in creating your own Actions. This week, we have Victoria Drake who has created a whole host of Actions.

#community #github #github action hero

Deploying my portfolio website on Github Pages using Github Actions.

I recently deployed  my portfolio site and wanted to try out github actions and this is my experience of automating the deployment.

This article is more focused on how you can use the GitHub actions and how easy it is to deploy your code to GitHub pages rather than the portfolio site code.So every time you make an update or build to your website ,the changes are automatically reflected and this automated deploying process makes work much faster.

The way GitHub action works is you create actions in your repositories by creating one or more yaml files and these are called workflows.Workflows now can handle build tasks like CI CD. This means you use the action to test your code and push the site to the desired hosting platform (in this case GitHub pages ) when the main branch changes .

First step assuming that you have a GitHub account is to create a repository having your website code in it.Now I have a bootstrap website but in the future I do plan on adding node JS so I already added package.json.

#workflow #portfolio #github #github-actions #github-pages