Compare commits

..

No commits in common. "af6309d249077cac662754627c0a97ca8cc7829b" and "e1271ab549bf91fc0affe4662727fc699d748e4c" have entirely different histories.

3 changed files with 6 additions and 6 deletions

View file

@ -7,10 +7,10 @@ on:
jobs:
build:
runs-on: docker
runs-on: ubuntu-latest
steps:
- name: Checkout
uses: https://github.com/actions/checkout@b4ffde65f46336ab88eb53be808477a3936bae11 # v4.1.1
uses: actions/checkout@b4ffde65f46336ab88eb53be808477a3936bae11 # v4.1.1
with:
token: ${{ secrets.MAINTAINER_TOKEN }}

View file

@ -7,10 +7,10 @@ on:
jobs:
build:
runs-on: docker
runs-on: ubuntu-latest
steps:
- name: Checkout
uses: https://github.com/actions/checkout@b4ffde65f46336ab88eb53be808477a3936bae11 # v4.1.1
uses: actions/checkout@b4ffde65f46336ab88eb53be808477a3936bae11 # v4.1.1
- name: Ref
shell: bash

View file

@ -1,4 +1,4 @@
# Forgejo action test: Subsequent workflows
# Gitea action test: Subsequent workflows
Is it possible to have subsequent workflow in Forgejo? Whenever I create a commit, gitea actions should tag it.
Is it possible to have subsequent workflow in Gitea? Whenever I create a commit, gitea actions should tag it.
On every tag gitea actions should be executed.