I&#39;m building Docker images with Github Actions and want to tag images with the branch name.

I found the `GITHUB_REF` variable, but it results in `refs/heads/feature-branch-1` and I need only `feature-branch-1`.


How to get the current branch within Github Actions?

In the new GitHub Actions, I am trying to install a package in order to use it in one of the next steps.

```yml
name: CI

on: [push, pull_request]

jobs:
  translations:
    runs-on: ubuntu-latest
    steps:
    - uses: actions/checkout@v1
      with:
        fetch-depth: 1
    - name: Install xmllint
      run: apt-get install libxml2-utils
    # ...
```

However this fails with

```
Run apt-get install libxml2-utils
  apt-get install libxml2-utils
  shell: /bin/bash -e {0}
E: Could not open lock file /var/lib/dpkg/lock-frontend - open (13: Permission denied)
E: Unable to acquire the dpkg frontend lock (/var/lib/dpkg/lock-frontend), are you root?
##[error]Process completed with exit code 100.
```

What&#39;s the best way to do this? Do I need to reach for Docker?

How to apt-get install in a GitHub Actions workflow?

I&#39;m relatively new to GitHub Actions and I have 2 jobs–one that runs my tests, and one that deploys my project onto a server.

Obviously I want the tests to run on every branch, but deploying should only happen when something gets pushed to master.

I&#39;m struggling to find a way to run a job on a specific branch. I know it&#39;s possible to only run *entire workflows* on a specific branch, however that would mean I would have a &quot;test&quot; workflow and a &quot;deploy&quot; workflow. 

This sounds like a solution, however they would run parallel. In an ideal world, the tests would run first, and only if they succeed, then the deploy job would start. This isn&#39;t the case when using 2 separate workflows.

How would I be able to achieve this? Is it possible to run **jobs** on a specific branch?

Only run job on specific branch with GitHub Actions

Getting 
&gt; refusing to allow an OAuth App to create or update workflow `.github/workflows/cd.yml` without `workflow` scope&quot;

on `git push`. How to grant `workflow` scope?

How to resolve &quot;refusing to allow an OAuth App to create or update workflow&quot; on git push

I&#39;ve just started exploring Github actions however I&#39;ve found myself placing a command in multiple places. 

I have a PHP project where the `composer.json` is not in the root, my structure looks like:

```
my-project:
    readme.md
    app:
        composer.json
```

Obviously there is more to it and there is a reason why, but my `composer.json` sits in a subdirectory called &#39;app&#39;. As a result in my workflow, I have to cd into that folder every time to run a command:

```yaml
name: CI

on: [push]

jobs:
  phpunit:
    runs-on: ubuntu-latest
    steps:
      - uses: actions/checkout@v1
      - name: Setup Symfony
        run: |
          cd app
          cp .env.dev .env
      - name: Install Composer Dependencies
        run: |
          cd app
          composer install --prefer-dist
      - name: Run Tests
        run: |
          cd app
          php bin/phpunit
```

How can I remove the `cd app` in every stage?

Running actions in another directory

In GitHub Actions, I&#39;d like to evaluate a bash expression and then assign it to an environment variable:

```yaml
    - name: Tag image
      env:
        GITHUB_SHA_SHORT: ${{ $(echo $GITHUB_SHA | cut -c 1-6) }}
      ..do other things...
```

However, this naive attempt has failed. [According to the docs][1] this doesn&#39;t seem to be supported; a somewhat clean workaround would be fine.

[1]: https://help.github.com/en/articles/contexts-and-expression-syntax-for-github-actions#literals

How do I set an env var with a bash expression in GitHub Actions?

I&#39;m trying to follow an example Github has for testing my build with github actions, and then compressing the test results and uploading them as an artifact.
https://help.github.com/en/actions/automating-your-workflow-with-github-actions/persisting-workflow-data-using-artifacts#uploading-build-and-test-artifacts

I&#39;m having trouble with what to do when my tests fail though. This is my action. When my tests pass everything works great, my results are zipped an exported as an artifact, but if my tests fail, it stops the rest of the steps in the job, so my results never get published.   
[![github-ci-result][1]][1]   
I tried adding the continue-on-error: true https://help.github.com/en/actions/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions#jobsjob_idstepscontinue-on-error    
This makes it continue after it fails and uploads my test results. but then the job is marked as passed, even though my test step failed. Is there some way to have it upload my artifact even if a step fails, while still marking the overall job as failed?

    name: CI
    on:
      pull_request:
        branches:
        - master
      push:
        branches:
          - master
          
    jobs:
      build-and-test:
        runs-on: ubuntu-latest
        steps:
        - uses: actions/checkout@v1    
        - name: Test App
          run: ./gradlew test
    
        - name: Archive Rest Results
          uses: actions/upload-artifact@v1
          with:
            name: test-results
            path: app/build/reports/tests


  [1]: https://i.stack.imgur.com/NFoGe.png

How to run a github-actions step, even if the previous step fails, while still failing the job

Trying to use Github&#39;s beta actions, I have two jobs, one that builds the code and then one that will deploy code. However, I can&#39;t seem to get the build artifact in deploy job.

My latest attempt is to manually set a container image with the same volumes for each job, according to docs this should be solution: https://help.github.com/en/articles/workflow-syntax-for-github-actions#jobsjob_idcontainervolumes

&gt; Sets an array of volumes for the container to use. You can use volumes to share data between services or other steps in a job. You can specify named Docker volumes, anonymous Docker volumes, or bind mounts on the host.

**Workflow**

    name: CI
    on:
      push:
        branches:
        - master
        paths:
        - .github/workflows/server.yml
        - server/*
    jobs:
      build:
        runs-on: ubuntu-latest
        container:
          image: docker://node:10
          volumes:
          - /workspace:/github/workspace
        steps:
        - uses: actions/checkout@master
        - run: yarn install
          working-directory: server
        - run: yarn build
          working-directory: server
        - run: yarn test
          working-directory: server
        - run: ls
          working-directory: server
      deploy:
        needs: build
        runs-on: ubuntu-latest
        container:
          image: docker://google/cloud-sdk:latest
          volumes:
          - /workspace:/github/workspace
        steps:
          - uses: actions/checkout@master
          - run: ls
            working-directory: server
          - run: gcloud --version


The first job (build) has a build directory, but when the second job (deploy) runs it doesn&#39;t and only contains the source code.

*This project is a mono repo with code I&#39;m trying to deploy being under path `server` hence all the `working-directory` flags.*

Github actions share workspace/artifacts between jobs?

Some of my GitHub Actions workflows started recently to return this error when installing Chromedriver:

```lang-none
Get:1 http://security.debian.org/debian-security buster/updates InRelease [65.4 kB]
Get:2 http://deb.debian.org/debian buster InRelease [122 kB]
Get:3 http://deb.debian.org/debian buster-updates InRelease [51.9 kB]
Reading package lists...
E: Repository &#39;http://security.debian.org/debian-security buster/updates InRelease&#39; changed its &#39;Suite&#39; value from &#39;stable&#39; to &#39;oldstable&#39;
E: Repository &#39;http://deb.debian.org/debian buster InRelease&#39; changed its &#39;Suite&#39; value from &#39;stable&#39; to &#39;oldstable&#39;
E: Repository &#39;http://deb.debian.org/debian buster-updates InRelease&#39; changed its &#39;Suite&#39; value from &#39;stable-updates&#39; to &#39;oldstable-updates&#39;
Error: Process completed with exit code 100.
```

Here is my step implementation:

```yaml
jobs:
  build:
    runs-on: ubuntu-latest
    container:
        image: docker://guillaumefalourd/ritchiecli:py-3.8
    steps:
      - name: Install Chrome Driver
        run: |
            sudo apt-get update
            sudo apt-get install -y unzip xvfb libxi6 libgconf-2-4 gnupg2
            sudo curl -sS -o - https://dl-ssl.google.com/linux/linux_signing_key.pub | apt-key add
            sudo echo &quot;deb https://dl.google.com/linux/chrome/deb/ stable main&quot; &gt;&gt; /etc/apt/sources.list.d/google-chrome.list
            sudo apt-get -y update
            sudo apt-get -y install google-chrome-stable
            wget -N https://chromedriver.storage.googleapis.com/89.0.4389.23/chromedriver_linux64.zip -P ~/
            unzip ~/chromedriver_linux64.zip -d ~/
            rm ~/chromedriver_linux64.zip
            sudo mv -f ~/chromedriver /usr/local/bin/chromedriver
            sudo chown root:root /usr/local/bin/chromedriver
            sudo chmod 0755 /usr/local/bin/chromedriver
```

Docker Image Implementation: [docker://guillaumefalourd/ritchiecli:py-3.8](https://github.com/GuillaumeFalourd/ritchie-docker-images/blob/master/py-3.8/Dockerfile)

## What I tried

1. I read from [here](https://www.reddit.com/r/debian/comments/ca3se6/for_people_who_gets_this_error_inrelease_changed/) and [here](https://superuser.com/questions/1456989/how-to-configure-apt-in-debian-buster-after-release) that adding `sudo apt-get --allow-releaseinfo-change update` or `sudo apt-get dist-upgrade` could resolve the problem, but even adding those to my workflow didn&#39;t resolve it.

2. I tried using this action [setup-chromedriver](https://github.com/marketplace/actions/setup-chromedriver) but it returned the same error when following the documentation:

    ```yaml
    steps:
    - uses: actions/checkout@v2
    - uses: nanasess/setup-chromedriver@master
      with:
        # Optional: do not specify to match Chrome&#39;s version
        chromedriver-version: &#39;88.0.4324.96&#39;
    - run: |
        export DISPLAY=:99
        chromedriver --url-base=/wd/hub &amp;
        sudo Xvfb -ac :99 -screen 0 1280x1024x24 &gt; /dev/null 2&gt;&amp;1 &amp; # optional
    ```

3. As it seems to be related to _[Debian 10][1] (Buster)_ (?) I also tried to use another Ubuntu runner version as a runner (`ubuntu-18.04` instead of `ubuntu-latest`), but nothing changed, same error.

### How can I resolve this issue?

* * *

&lt;hr/&gt;

### Answer

*I observed afterwards that the problem was happening at the first command : `sudo apt-get update` (and I was adding the other command after...).*

*Substituting it for `sudo apt-get --allow-releaseinfo-change update` resolved my problem.*

*Therefore the answer was not to add the `sudo apt-get --allow-releaseinfo-change update` to the step executed commands, but **substituting** the `sudo apt-get update` command for it.*

```yaml
jobs:
  build:
    runs-on: ubuntu-latest
    container:
        image: docker://guillaumefalourd/ritchiecli:py-3.8
    steps:
      - name: Install Chrome Driver
        run: |
            sudo apt-get --allow-releaseinfo-change update
            sudo apt-get install -y unzip xvfb libxi6 libgconf-2-4 gnupg2
            sudo curl -sS -o - https://dl-ssl.google.com/linux/linux_signing_key.pub | apt-key add
            sudo echo &quot;deb https://dl.google.com/linux/chrome/deb/ stable main&quot; &gt;&gt; /etc/apt/sources.list.d/google-chrome.list
            sudo apt-get -y update
            sudo apt-get -y install google-chrome-stable
            wget -N https://chromedriver.storage.googleapis.com/89.0.4389.23/chromedriver_linux64.zip -P ~/
            unzip ~/chromedriver_linux64.zip -d ~/
            rm ~/chromedriver_linux64.zip
            sudo mv -f ~/chromedriver /usr/local/bin/chromedriver
            sudo chown root:root /usr/local/bin/chromedriver
            sudo chmod 0755 /usr/local/bin/chromedriver
```

  [1]: https://en.wikipedia.org/wiki/Debian_version_history#Debian_10_(Buster)



Repository &#39;http://security.debian.org/debian-security buster/updates InRelease&#39; changed its &#39;Suite&#39; value from &#39;stable&#39; to &#39;oldstable&#39;

I am planning to move our Travis CI build to GitHub Actions using Docker for our per-commit testing.

Can I reproducibly run these new GitHub Actions workflows locally? Is there a generic way to run any GitHub Actions workflow locally?

How to run GitHub Actions workflows locally?

I have a Github action command that is really long:

    name: build

    on: [push]

    jobs:
        build:
            runs-on: ubuntu-18.04
            steps:
                - uses: actions/checkout@v1
                - name: Install Prerequisites
                  run: |
                    sudo apt-get update
                    sudo apt-get install -y --no-install-recommends &quot;a very very long list of prerequisites&quot;

May I know whether it is possible to split the long command into multiple lines for better readability? I have tried the separator &#39;\&#39; but it does not work. Thanks in advance.

Github Action: Split Long Command into Multiple Lines

I create a couple workflows in the `.github/workflows` folder of my repository to experiment with GitHub Actions. I have since learned quite a bit and deleted said &quot;experimental&quot; workflows from my repo. After deleting the &quot;experimental&quot; workflow yaml files and committing the deletions, when I go to the Actions tab of my repository I **STILL** see the workflows that I have since deleted.

I see no option to delete and start from scratch?! Is this not possible? Is it maybe possible through GitHub API? Hmm.

Delete a workflow from GitHub Actions

I have a monorepo with two workflows:

`.github/workflows/test.yml`


    name: test

    on: [push, pull_request]

    jobs:
      test-packages:
        runs-on: ubuntu-latest
        steps:
          - uses: actions/checkout@v1
          - name: test packages
            run: |
              yarn install
              yarn test
    ...

`.github/workflows/deploy.yml`

    name: deploy

    on:
      push:
        tags:
          - &quot;*&quot;

    jobs:
      deploy-packages:
        runs-on: ubuntu-latest
        needs: test-packages
        steps:
          - uses: actions/checkout@v1
          - name: deploy packages
            run: |
              yarn deploy
            env:
              NODE_AUTH_TOKEN: ${{ secrets.NPM_TOKEN }}
    ...

This doesn&#39;t work, I can&#39;t reference a job in another workflow:

    ### ERRORED 19:13:07Z

    - Your workflow file was invalid: The pipeline is not valid. The pipeline must contain at least one job with no dependencies.

**Is there a way to create a dependency between workflows?**

What I want is to run `test.yml` then `deploy.yml` on tags, and `test.yml` only on push and pull requests. I don&#39;t want to duplicate jobs between workflows.

Dependencies Between Workflows on Github Actions

I have been using github actions for quite sometime but today my deployments started failing. Below is the error from github action logs

```
Command: git
Arguments: ls-remote --tags --heads git://github.com/adobe-webplatform/eve.git
Directory: /home/runner/work/stackstream-fe/stackstream-fe
Output:
fatal: remote error: 
  The unauthenticated git protocol on port 9418 is no longer supported.
```
Upon investigation, it appears that below section in my yml file is causing the issue. 

        - name: Installing modules
          run: yarn install

I have looked into [this change log][1] but can&#39;t seem to comprehend the issue. 


Additional Details:
Server: **EC2 Instance** 
Github actions steps:

      steps:
      - name: Checkout
        uses: actions/checkout@v2

      - id: vars
        run: |
          if [ &#39;${{ github.ref }}&#39; == &#39;refs/heads/master&#39; ]; then echo &quot;::set-output name=environment::prod_stackstream&quot; ; echo &quot;::set-output name=api-url::api&quot; ; elif [ &#39;${{ github.ref }}&#39; == &#39;refs/heads/staging&#39; ]; then echo &quot;::set-output name=environment::staging_stackstream&quot;  ; echo &quot;::set-output name=api-url::stagingapi&quot; ; else echo &quot;::set-output name=environment::dev_stackstream&quot; ; echo &quot;::set-output name=api-url::devapi&quot; ; fi

      - uses: pCYSl5EDgo/cat@master
        id: slack
        with:
          path: .github/workflows/slack.txt

      - name: Slack Start Notification
        uses: 8398a7/action-slack@v3
        env:
          SLACK_WEBHOOK_URL: ${{ secrets.SLACK_WEBHOOK_URL }}
          ENVIRONMENT: &#39;`${{ steps.vars.outputs.environment }}`&#39;
          COLOR: good
          STATUS: &#39;`Started`&#39;
        with:
          status: custom
          fields: workflow,job,commit,repo,ref,author,took
          custom_payload: |
            ${{ steps.slack.outputs.text }}

      - name: Installing modules
        env:
          REACT_APP_API_URL: &#39;https://${{ steps.vars.outputs.api-url }}mergestack.com/api/v1&#39;
        run: yarn install

      - name: Create Frontend Build
        env:
          REACT_APP_API_URL: &#39;https://${{ steps.vars.outputs.api-url }}mergestack.com/api/v1&#39;
        run: yarn build

      - name: Deploy to Frontend Server DEV
        if: ${{ contains(github.ref, &#39;dev&#39;) }}
        uses: easingthemes/ssh-deploy@v2.1.5
        env:
          SSH_PRIVATE_KEY: ${{ secrets.DEV_KEY }}
          ARGS: &#39;-rltgoDzvO --delete&#39;
          SOURCE: &#39;deploy/&#39;
          REMOTE_HOST: ${{ secrets.DEV_HOST }}
          REMOTE_USER: plyfolio-dev
          TARGET: &#39;/home/plyfolio-dev/${{ steps.vars.outputs.environment }}/fe/deploy&#39;


**package.json** file 

       {
      &quot;name&quot;: &quot;stackstream-fe&quot;,
      &quot;version&quot;: &quot;1.0.0&quot;,
      &quot;authors&quot;: [
        &quot;fayyaznofal@gmail.com&quot;
      ],
      &quot;private&quot;: true,
      &quot;dependencies&quot;: {
        &quot;@fortawesome/fontawesome-svg-core&quot;: &quot;^1.2.34&quot;,
        &quot;@fortawesome/free-solid-svg-icons&quot;: &quot;^5.15.2&quot;,
        &quot;@fortawesome/react-fontawesome&quot;: &quot;^0.1.14&quot;,
        &quot;@fullcalendar/bootstrap&quot;: &quot;^5.5.0&quot;,
        &quot;@fullcalendar/core&quot;: &quot;^5.5.0&quot;,
        &quot;@fullcalendar/daygrid&quot;: &quot;^5.5.0&quot;,
        &quot;@fullcalendar/interaction&quot;: &quot;^5.5.0&quot;,
        &quot;@fullcalendar/react&quot;: &quot;^5.5.0&quot;,
        &quot;@lourenci/react-kanban&quot;: &quot;^2.1.0&quot;,
        &quot;@redux-saga/simple-saga-monitor&quot;: &quot;^1.1.2&quot;,
        &quot;@testing-library/jest-dom&quot;: &quot;^5.11.9&quot;,
        &quot;@testing-library/react&quot;: &quot;^11.2.3&quot;,
        &quot;@testing-library/user-event&quot;: &quot;^12.6.0&quot;,
        &quot;@toast-ui/react-chart&quot;: &quot;^1.0.2&quot;,
        &quot;@types/jest&quot;: &quot;^26.0.14&quot;,
        &quot;@types/node&quot;: &quot;^14.10.3&quot;,
        &quot;@types/react&quot;: &quot;^16.9.49&quot;,
        &quot;@types/react-dom&quot;: &quot;^16.9.8&quot;,
        &quot;@vtaits/react-color-picker&quot;: &quot;^0.1.1&quot;,
        &quot;apexcharts&quot;: &quot;^3.23.1&quot;,
        &quot;availity-reactstrap-validation&quot;: &quot;^2.7.0&quot;,
        &quot;axios&quot;: &quot;^0.21.1&quot;,
        &quot;axios-mock-adapter&quot;: &quot;^1.19.0&quot;,
        &quot;axios-progress-bar&quot;: &quot;^1.2.0&quot;,
        &quot;bootstrap&quot;: &quot;^5.0.0-beta2&quot;,
        &quot;chart.js&quot;: &quot;^2.9.4&quot;,
        &quot;chartist&quot;: &quot;^0.11.4&quot;,
        &quot;classnames&quot;: &quot;^2.2.6&quot;,
        &quot;components&quot;: &quot;^0.1.0&quot;,
        &quot;dotenv&quot;: &quot;^8.2.0&quot;,
        &quot;draft-js&quot;: &quot;^0.11.7&quot;,
        &quot;echarts&quot;: &quot;^4.9.0&quot;,
        &quot;echarts-for-react&quot;: &quot;^2.0.16&quot;,
        &quot;firebase&quot;: &quot;^8.2.3&quot;,
        &quot;google-maps-react&quot;: &quot;^2.0.6&quot;,
        &quot;history&quot;: &quot;^4.10.1&quot;,
        &quot;i&quot;: &quot;^0.3.6&quot;,
        &quot;i18next&quot;: &quot;^19.8.4&quot;,
        &quot;i18next-browser-languagedetector&quot;: &quot;^6.0.1&quot;,
        &quot;jsonwebtoken&quot;: &quot;^8.5.1&quot;,
        &quot;leaflet&quot;: &quot;^1.7.1&quot;,
        &quot;lodash&quot;: &quot;^4.17.21&quot;,
        &quot;lodash.clonedeep&quot;: &quot;^4.5.0&quot;,
        &quot;lodash.get&quot;: &quot;^4.4.2&quot;,
        &quot;metismenujs&quot;: &quot;^1.2.1&quot;,
        &quot;mkdirp&quot;: &quot;^1.0.4&quot;,
        &quot;moment&quot;: &quot;2.29.1&quot;,
        &quot;moment-timezone&quot;: &quot;^0.5.32&quot;,
        &quot;nouislider-react&quot;: &quot;^3.3.9&quot;,
        &quot;npm&quot;: &quot;^7.6.3&quot;,
        &quot;prop-types&quot;: &quot;^15.7.2&quot;,
        &quot;query-string&quot;: &quot;^6.14.0&quot;,
        &quot;react&quot;: &quot;^16.13.1&quot;,
        &quot;react-apexcharts&quot;: &quot;^1.3.7&quot;,
        &quot;react-auth-code-input&quot;: &quot;^1.0.0&quot;,
        &quot;react-avatar&quot;: &quot;^3.10.0&quot;,
        &quot;react-bootstrap&quot;: &quot;^1.5.0&quot;,
        &quot;react-bootstrap-editable&quot;: &quot;^0.8.2&quot;,
        &quot;react-bootstrap-sweetalert&quot;: &quot;^5.2.0&quot;,
        &quot;react-bootstrap-table-next&quot;: &quot;^4.0.3&quot;,
        &quot;react-bootstrap-table2-editor&quot;: &quot;^1.4.0&quot;,
        &quot;react-bootstrap-table2-paginator&quot;: &quot;^2.1.2&quot;,
        &quot;react-bootstrap-table2-toolkit&quot;: &quot;^2.1.3&quot;,
        &quot;react-chartist&quot;: &quot;^0.14.3&quot;,
        &quot;react-chartjs-2&quot;: &quot;^2.11.1&quot;,
        &quot;react-color&quot;: &quot;^2.19.3&quot;,
        &quot;react-confirm-alert&quot;: &quot;^2.7.0&quot;,
        &quot;react-content-loader&quot;: &quot;^6.0.1&quot;,
        &quot;react-countdown&quot;: &quot;^2.3.1&quot;,
        &quot;react-countup&quot;: &quot;^4.3.3&quot;,
        &quot;react-cropper&quot;: &quot;^2.1.4&quot;,
        &quot;react-data-table-component&quot;: &quot;^6.11.8&quot;,
        &quot;react-date-picker&quot;: &quot;^8.0.6&quot;,
        &quot;react-datepicker&quot;: &quot;^3.4.1&quot;,
        &quot;react-dom&quot;: &quot;^16.13.1&quot;,
        &quot;react-draft-wysiwyg&quot;: &quot;^1.14.5&quot;,
        &quot;react-drag-listview&quot;: &quot;^0.1.8&quot;,
        &quot;react-drawer&quot;: &quot;^1.3.4&quot;,
        &quot;react-dropzone&quot;: &quot;^11.2.4&quot;,
        &quot;react-dual-listbox&quot;: &quot;^2.0.0&quot;,
        &quot;react-facebook-login&quot;: &quot;^4.1.1&quot;,
        &quot;react-flatpickr&quot;: &quot;^3.10.6&quot;,
        &quot;react-google-login&quot;: &quot;^5.2.2&quot;,
        &quot;react-hook-form&quot;: &quot;^7.15.2&quot;,
        &quot;react-i18next&quot;: &quot;^11.8.5&quot;,
        &quot;react-icons&quot;: &quot;^4.2.0&quot;,
        &quot;react-image-lightbox&quot;: &quot;^5.1.1&quot;,
        &quot;react-input-mask&quot;: &quot;^2.0.4&quot;,
        &quot;react-jvectormap&quot;: &quot;^0.0.16&quot;,
        &quot;react-leaflet&quot;: &quot;^3.0.5&quot;,
        &quot;react-meta-tags&quot;: &quot;^1.0.1&quot;,
        &quot;react-modal-video&quot;: &quot;^1.2.6&quot;,
        &quot;react-notifications&quot;: &quot;^1.7.2&quot;,
        &quot;react-number-format&quot;: &quot;^4.7.3&quot;,
        &quot;react-perfect-scrollbar&quot;: &quot;^1.5.8&quot;,
        &quot;react-rangeslider&quot;: &quot;^2.2.0&quot;,
        &quot;react-rating&quot;: &quot;^2.0.5&quot;,
        &quot;react-rating-tooltip&quot;: &quot;^1.1.6&quot;,
        &quot;react-redux&quot;: &quot;^7.2.1&quot;,
        &quot;react-responsive-carousel&quot;: &quot;^3.2.11&quot;,
        &quot;react-router-dom&quot;: &quot;^5.2.0&quot;,
        &quot;react-script&quot;: &quot;^2.0.5&quot;,
        &quot;react-scripts&quot;: &quot;3.4.3&quot;,
        &quot;react-select&quot;: &quot;^4.3.1&quot;,
        &quot;react-sparklines&quot;: &quot;^1.7.0&quot;,
        &quot;react-star-ratings&quot;: &quot;^2.3.0&quot;,
        &quot;react-super-responsive-table&quot;: &quot;^5.2.0&quot;,
        &quot;react-switch&quot;: &quot;^6.0.0&quot;,
        &quot;react-table&quot;: &quot;^7.6.3&quot;,
        &quot;react-toastify&quot;: &quot;^7.0.3&quot;,
        &quot;react-toastr&quot;: &quot;^3.0.0&quot;,
        &quot;react-twitter-auth&quot;: &quot;0.0.13&quot;,
        &quot;reactstrap&quot;: &quot;^8.8.1&quot;,
        &quot;recharts&quot;: &quot;^2.0.8&quot;,
        &quot;redux&quot;: &quot;^4.0.5&quot;,
        &quot;redux-saga&quot;: &quot;^1.1.3&quot;,
        &quot;reselect&quot;: &quot;^4.0.0&quot;,
        &quot;sass&quot;: &quot;^1.37.5&quot;,
        &quot;simplebar-react&quot;: &quot;^2.3.0&quot;,
        &quot;styled&quot;: &quot;^1.0.0&quot;,
        &quot;styled-components&quot;: &quot;^5.2.1&quot;,
        &quot;toastr&quot;: &quot;^2.1.4&quot;,
        &quot;typescript&quot;: &quot;^4.0.2&quot;,
        &quot;universal-cookie&quot;: &quot;^4.0.4&quot;
      },
      &quot;devDependencies&quot;: {
        &quot;@typescript-eslint/eslint-plugin&quot;: &quot;^2.27.0&quot;,
        &quot;@typescript-eslint/parser&quot;: &quot;^2.27.0&quot;,
        &quot;@typescript-eslint/typescript-estree&quot;: &quot;^4.15.2&quot;,
        &quot;eslint-config-prettier&quot;: &quot;^6.10.1&quot;,
        &quot;eslint-plugin-prettier&quot;: &quot;^3.1.2&quot;,
        &quot;husky&quot;: &quot;^4.2.5&quot;,
        &quot;lint-staged&quot;: &quot;^10.1.3&quot;,
        &quot;prettier&quot;: &quot;^1.19.1&quot;,
        &quot;react-test-renderer&quot;: &quot;^16.13.1&quot;,
        &quot;redux-devtools-extension&quot;: &quot;^2.13.8&quot;,
        &quot;redux-mock-store&quot;: &quot;^1.5.4&quot;
      },
      &quot;scripts&quot;: {
        &quot;start&quot;: &quot;react-scripts start&quot;,
        &quot;build&quot;: &quot;react-scripts build &amp;&amp; mv build ./deploy/build&quot;,
        &quot;build-local&quot;: &quot;react-scripts build&quot;,
        &quot;test&quot;: &quot;react-scripts test&quot;,
        &quot;eject&quot;: &quot;react-scripts eject&quot;
      },
      &quot;eslintConfig&quot;: {
        &quot;extends&quot;: &quot;react-app&quot;
      },
      &quot;husky&quot;: {
        &quot;hooks&quot;: {
          &quot;pre-commit&quot;: &quot;lint-staged&quot;
        }
      },
      &quot;lint-staged&quot;: {
        &quot;*.{js,ts,tsx}&quot;: [
          &quot;eslint --fix&quot;
        ]
      },
      &quot;browserslist&quot;: {
        &quot;production&quot;: [
          &quot;&gt;0.2%&quot;,
          &quot;not dead&quot;,
          &quot;not op_mini all&quot;
        ],
        &quot;development&quot;: [
          &quot;last 1 chrome version&quot;,
          &quot;last 1 firefox version&quot;,
          &quot;last 1 safari version&quot;
        ]
      }
    }

**[package-lock.json][2]**


  [1]: https://github.blog/2021-09-01-improving-git-protocol-security-github
  [2]: https://gist.github.com/nofalfayyaz/ae2ceeda8d61af19a2ab6c45f80822a7

The unauthenticated git protocol on port 9418 is no longer supported

When I create a GitHub Actions workflow file, the example YAML file contains `runs-on: ubuntu-latest`. [According to the docs](https://help.github.com/en/articles/virtual-environments-for-github-actions#supported-virtual-environments), I only have the options between a couple versions of Ubuntu, Windows Server and macOS X.

I thought GitHub Actions runs inside Docker. How do I choose my Docker image?

How do I use Docker with GitHub Actions?

I&#39;m running a workflow on some Operating systems.

However, there is a specific step that I have to run only on Ubuntu:

    runs-on: ${{ matrix.os }}
    strategy:
        matrix:
            os: [ubuntu-latest, windows-latest, macOS-latest]
    steps:
        - name: Setup Ubuntu
          run : export DISPLAY=&quot;127.0.0.1:10.0&quot;
          if: # --&gt; What should be here? &lt;--
I couldn&#39;t find any examples nor explanation on how to run steps on specific OSes. 

Can somebody help?

Github Actions: Run step on specific OS

Is there a way to access the current tag that has been pushed in a Github Action? In CircleCI you can access this value with the `$CIRCLE_TAG` variable.

My Workflow yaml is being triggered by a tag like so:
```
on:
  push:
    tags:
      - &#39;v*.*.*&#39;
```
And I want to use that version number as a file path later on in the workflow.


Get the current pushed tag in Github Actions

Normally, my pipelines take 15 minutes to execute. 

Recently, for some strange reasons, some pipelines take between 45 minutes and 6 hours to fail.

Is it possible to set a default timeout limit on GitHub Action&#39;s pipeline (for example, auto cancel after 30 minutes)?



Set default Timeout on Github action pipeline

What is the right way for running multiple commands in one `action`?

## For example:

I want to run a python script as `action`. Before running this script I need to install the `requirements.txt`.

### I can think of several options:

 - Create a `Dockerfile` with the command `RUN pip install -r requirements.txt` in it.
 - Use the `python:3` image, and run the `pip install -r requirements.txt` in the `entrypoint.sh` file before running the arguments from `args` in `main.workflow`.
 - use both `pip install` and `python myscript.py` as `args`

## Another example:

I want to run a script that exists in my repository, then compare 2 files (its output and a file that already exists).

This is a process that includes **two commands**, whereas in the first example, the `pip install` command can be considered **a building command** rather than a test command.

## the question:

Can I create another Docker for another command, which will contain the output of the previous Docker?

I&#39;m looking for guidelines for the location of the command in `Dockerfile`, in `entrypoint` or in `args`.

How to run multiple commands in one Github Actions Docker

Say I have a GitHub actions workflow with 2 steps.

1. Download and compile my application&#39;s dependencies.
2. Compile and test my application

My dependencies rarely change and the compiled dependencies can be safely cached until I next change the lock-file that specifies their versions.

Is a way to save the result of the first step so that in future workflow can skip over that step?

How do I cache steps in GitHub actions?

For (mainly) pedagogical reasons, I&#39;m trying to run this workflow in GitHub actions:

```yaml
name: &quot;We &#127892; Perl&quot;
on:
  issues:
    types: [opened, edited, milestoned]

jobs:
  seasonal_greetings:
    runs-on: windows-latest
    steps:
      - name: Maybe greet
        id: maybe-greet
        env:
          HEY: &quot;Hey you!&quot;
          GREETING: &quot;Merry Xmas to you too!&quot;
          BODY: ${{ github.event.issue.body }}
        run: |
          $output=(perl -e &#39;print ($ENV{BODY} =~ /Merry/)?$ENV{GREETING}:$ENV{HEY};&#39;)
          Write-Output &quot;::set-output name=GREET::$output&quot;
  produce_comment:
    name: Respond to issue
    runs-on: ubuntu-latest
    steps:
      - name: Dump job context
        env:
          JOB_CONTEXT: ${{ jobs.maybe-greet.steps.id }}
        run: echo &quot;$JOB_CONTEXT&quot;
```

I need two different jobs, since they use different context (operating systems), but I need to get the output of a step in the first job to the second job. I am trying with several combinations of the `jobs` context as found [here](https://help.github.com/en/actions/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions#jobsjob_idif) but there does not seem to be any way to do that. Apparently, `jobs` is just the name of a YAML variable that does not really have a context, and the context `job` contains just the success or failure. Any idea?

Using output from a previous job in a new one in a GitHub Action

I want to be able to let an action run on any given branch except master.
I am aware that there is a prebuilt `filter` action, but I want the exact opposite. 

More like GitLab&#39;s `except` keyword. 
Since this is not inside the official docs, has anyone prepared a decent workaround?

Thank you very much.

GitHub Actions: how to target all branches EXCEPT master?

I&#39;m trying to push to `origin` remote from GitHub action. The logic of my action is:

 - handle `pull_request_review` events and filter by comment message
 - checkout to master, merge PR branch, run some checks and push it to `origin`

The script is:
```bash
if [[ &quot;${GITHUB_EVENT_NAME}&quot; != &quot;pull_request_review&quot; ]]; then
  echo &quot;unsupported event: ${GITHUB_EVENT_NAME}&quot;
  exit 1
fi

user=$(jq -r .review.user.login ${GITHUB_EVENT_PATH})
cmd=$(jq -r .review.body ${GITHUB_EVENT_PATH})
echo &quot;reviewer is ${user}, command is ${cmd}&quot;

if [[ &quot;${cmd}&quot; == &quot;merge&quot; ]]; then
  head=$(jq -r .pull_request.head.ref ${GITHUB_EVENT_PATH})
  git config user.email test@test.com
  git config user.name test
  git checkout -B _tmp origin/${head}
  git checkout -B master origin/master
  git merge --no-ff _tmp
  git push origin master
fi
```
I&#39;m running this script from `alpine:3.10` Docker container:
```Dockerfile
FROM alpine:3.10

LABEL &quot;com.github.actions.name&quot;=&quot;Hello world action&quot;
LABEL &quot;com.github.actions.icon&quot;=&quot;shield&quot;
LABEL &quot;com.github.actions.color&quot;=&quot;green&quot;

WORKDIR /app
COPY action.sh action.sh
RUN apk --update add bash git jq
CMD [&quot;bash&quot;, &quot;/app/action.sh&quot;]
```

First steps are working fine (checkout and merge), but action failed to push the merge to `origin` because of the error:
&gt; \+ git push origin master&lt;br/&gt;
&gt; fatal: could not read Username for &#39;https://github.com&#39;: No such device or address

It looks like GitHub-action Docker container is not configured to push to GitHub. How can I configure it? Is it possible to use some of the [env variables](https://help.github.com/en/articles/virtual-environments-for-github-actions#environment-variables) provided by GitHub or maybe some mounted files (like in `/github/*` path)?

Push to origin from GitHub action

I have one action (a `yaml` file) for deploying a docker image to Google Cloud Run.

I would like to receive Slack or Email messages informing the build and push results.

How could the message action be triggered after build action is completed?

Is it possible to get the result of the build action?

Github Actions - trigger another action after one action is completed

I recently hooked up my project with github actions for continuous integration. I created two separate jobs: the first one checks if the code in the pull request is accepted by our linter, and the second one checks if the code passes the test suite. I like that having two jobs like this shows up as two separate checkmarks in the Github webpage for the pull request:

[![enter image description here][1]][1]

The problem I&#39;m having now is that there is some **duplicated code in workflow YAML file**: the first 3 steps, which install Lua and Luarocks. Not only is it annoying to maintain, but it also **wastes CI minutes** by running the same actions twice. Is there a way to avoid this? So that the **setup code is only written in one place, and only runs once** when the workflow executes?

But I am confused what would be the proper way to proceed:
 1. Should I create my own Github Action with the shared setup code?
 2. Should I create a Docker image that already has Lua and Luarocks pre-installed?
 3. Should I use a single job? Can I still have independent checkmarks for the linter and the test suite if they are steps of the same job?
 4. Something else?

Here is the current YAML file for my workflow:

```yaml
name: Github Actions CI

on: [ pull_request ]

jobs:
    lint:
        name: Lint
        runs-on: ubuntu-latest
        steps:
            - uses: actions/checkout@v2
            - uses: leafo/gh-actions-lua@v8.0.0
            - uses: leafo/gh-actions-luarocks@v4.0.0

            - run: luarocks install luacheck
            - run: ./run-linter.sh

    test:
        name: Test
        runs-on: ubuntu-latest
        steps:
            - uses: actions/checkout@v2
            - uses: leafo/gh-actions-lua@v8.0.0
            - uses: leafo/gh-actions-luarocks@v4.0.0

            - run: luarocks install busted
            - run: ./build-project.sh
            - run: ./run-test-suite.sh
```

I tried searching for similar questions but couldn&#39;t find anything that exactly answered my question:

1. [Caching APT packages in GitHub Actions workflow](https://stackoverflow.com/questions/59269850/): I can&#39;t use this solution because I don&#39;t have a way to precisely specify all the versions of all the dependencies that I am using, so that they may be cached. I also don&#39;t mind if separate runs of the workflow are not cached. I&#39;m more worried about the code duplication.
2. [Github actions share workspace/artifacts between jobs?](https://stackoverflow.com/questions/57498605/github-actions-share-workspace-artifacts-between-jobs) I don&#39;t want to have to manage uploading uploading artifacts to a separate service and then deleting them afterwards.
3. [Reuse portion of github action across jobs](https://stackoverflow.com/questions/59757355/reuse-portion-of-github-action-across-jobs): In that question the only difference between the jobs is a single variable, so accepted answer is to use a build matrix. But I don&#39;t think a build matrix would work as well in my case, where only the setup code is the same?

  [1]: https://i.stack.imgur.com/9N2Gl.png

In a github actions workflow, is there a way to have multiple jobs reuse the same setup?

I have a GitHub action workflow file @ myrepo/.github/workflows/Build Webpage.yml it contains this: 

&lt;!-- language: lang-yaml --&gt;

    name: Webpage Build
    
    on:
      push:
        branches:
          - webpage 
        
    jobs:
      build:
        runs-on: ubuntu-latest
        steps:
        - uses: actions/checkout@v2
        - name: setup node
          uses: actions/setup-node@v2-beta
          with:
            node-version: &#39;12&#39;
        - name: install deps and predeploy
          run: |
            npm ci
            npm run predeploy
        - name: Deploy 
          uses: JamesIves/github-pages-deploy-action@3.5.2
          with:
            GITHUB_TOKEN: ${{secrets.GITHUB_TOKEN}}
            BRANCH: gh-pages
            FOLDER: build
When I push to the webpage branch nothing happens in the actions tab at all I can&#39;t tell if I have a syntax error or if something is completely not set up correctly, I have in past on this repo had errors relating to syntax like `every step must define a &#39;uses&#39; or &#39;run&#39; key`  which to me shows Github does recognize the workflow


GitHub Action workflow not running

I have a fairly basic scenario. I made a dedicated ssh key for this purpose and added it to my repository secrets.

1. Code gets pushed to `master`

2. GitHub action uploads it to server using `ssh` by doing `echo &quot;${{ secrets.SSH_KEY }}&quot; &gt; key`.

3. After that I can use this key to connect to my server e.g. `ssh -i key devops@myserver.com lsb_release -a`

The problem is that for some reason GitHub actions cannot write it to file, it writes characters `***` instead of the actual secret value into the file. Therefore obviously I cannot connect to my server.

How can I connect with ssh using this secret? Is there a way to connect without using a file? Can someone who did this common scenario using GitHub actions shed some light?

How can I extract secrets using GitHub Actions?

I&#39;m trying to build a GitHub workflow that will be triggered when another repository creates a new release.

In the documentation, there is the paragraph: [`on.event_name.types`](https://help.github.com/en/articles/workflow-syntax-for-github-actions#onevent_nametypes) where `event_name` will be `release`.

The question is: Is there any way to refer to the `release` event of another repository?

All Github Actions Solutions on Gang of Coders

Total of 28 Github Actions Solutions