forgejo-release/.forgejo/workflows/tests.yml

on: [ pull_request, push ]
jobs:
  integration:
    runs-on: docker
    steps:
      - uses: actions/checkout@v4

      - name: Unit tests of the supporting script forgejo-release.sh
        run: |
          testdata/forgejo-release-test.sh test_system_tea_bin
          testdata/forgejo-release-test.sh test_download_tea_bin
          testdata/forgejo-release-test.sh test_maybe_sign_release
also run CI on pull requests 2024-01-03 21:45:50 +01:00			`on: [ pull_request, push ]`
GPG signing logic 2023-05-26 13:03:49 +02:00			`jobs:`
			`integration:`
s/ubuntu-latest/docker/ 2023-11-05 22:30:57 +01:00			`runs-on: docker`
GPG signing logic 2023-05-26 13:03:49 +02:00			`steps:`
Update actions/checkout action to v4 2025-04-13 08:31:08 +00:00			`- uses: actions/checkout@v4`
GPG signing logic 2023-05-26 13:03:49 +02:00
			`- name: Unit tests of the supporting script forgejo-release.sh`
			`run: \|`
feat: use tea binary from system if available (#53) As a proposal solution to this issue: https://code.forgejo.org/actions/forgejo-release/issues/51 We use the system installed tea binary if available or download it as it was done before if not. The location of the binary is stored in a new variable `$TEA_BIN` which replaces the need for the `$ BIN_DIR` location. I tested it on Alpine and Debian. Co-authored-by: Rayan Mestiri <rayan.mestiri@gmail.com> Co-authored-by: Rayan MESTIRI <rayan.mestiri@NLGRSSL600K.ratpsmart.local> Reviewed-on: https://code.forgejo.org/actions/forgejo-release/pulls/53 Reviewed-by: earl-warren <earl-warren@noreply.code.forgejo.org> Co-authored-by: sheik <sheik@noreply.code.forgejo.org> Co-committed-by: sheik <sheik@noreply.code.forgejo.org> 2025-06-28 20:36:41 +00:00			`testdata/forgejo-release-test.sh test_system_tea_bin`
			`testdata/forgejo-release-test.sh test_download_tea_bin`
			`testdata/forgejo-release-test.sh test_maybe_sign_release`