After my Pull Request is created, my GitHub Action will start executing and the result will appear directly at the end of my Pull Request. Uses : actions/setup : node-version : 12.x On : push : branches : pull_request : branches : jobs : build : runs-on : ubuntu -latest

You can change master to main if your main branch has that name. We can configure it to run immediately after each push to any of our branches (including the master branch). The first thing is to define when we want the GitHub Action to run. You can see the code in the project repository in my Github profile. I have created a sample application in React with a small image component and some accessibility bugs. Since we have seen what GitHub Actions are, let’s see how we can use them to test the accessibility of your source code hosted on GitHub. Using GitHub Actions to automate accessibility tests The workflow configuration to define events, tasks, and steps to be executed in GitHub Actions are defined using YAML files that must be located in the. Github defines a workflow as a configurable automated process made up of one or more jobs. With GitHub Actions you could execute a series of statements and commands after a specific event has occurred, simply put, it’s your own pipeline CI / CD directly in your repository.

GitHub Actions allow you to automate, customize, and execute your software development workflows right in your repository with GitHub Actions. Puedes leer este artículo en español GitHub Actions But first, let’s define what GitHub Actions are and their workflows. Automating the accessibility tests of your source code with GitHub Actions #accessibility #development #react #GitHubĪutomating your accessibility tests with libraries like axe, pa11y, lighthouse, or unit tests directly in your GitHub repository is really easy with GitHub Actions.

Npm install from github example