Description
I have a main workflow with reuse:
name: Call a reusable workflow
on:
workflow_dispatch:
jobs:
build:
uses: test/shared/.gitea/workflows/test.yaml@master
test.yaml:
name: reusable CI
on:
workflow_call:
jobs:
build:
steps:
- name: Check workflow context
run: |
echo "Workflow called from: ${{ github.repository }}"
echo "Event name: ${{ github.event_name }}"
echo "Runner_OS: ${{ runner.os }}"
- name: Check repository structure
run: |
echo "Current directory: $(pwd)"
echo "Files:"
ls -la
echo "Repository contents:"
- name: check-reusable-123456789
run: |
echo "=== REUSABLE WORKFLOW VERSION 5.0 ==="
The problem is that the file being called is cached on the runner, and if I change it and rerun the workflow, nothing changes and the file is taken from the cache.
I haven't found a way to control this behavior (cache).
expression 'success()' evaluated to 'true'
☁ git clone 'https://git.reddigital.ru/test/shared' # ref=master
cloning https://git.xxx.com/test/shared to /root/.cache/act/test-shared@master
Provided ref is not a sha. Checking out branch before pulling changes
Cloned https://git.xxx.com/test/shared to /root/.cache/act/test-shared@master
Provided ref is not a sha. Updating branch ref after pull
Checked out master
evaluating expression 'success()'
expression 'success()' evaluated to 'true'
Gitea Version
1.25.4
Can you reproduce the bug on the Gitea demo site?
Yes
Log Gist
No response
Screenshots
No response
Git Version
No response
Operating System
No response
How are you running Gitea?
docker
Database
SQLite
Description
I have a main workflow with reuse:
test.yaml:
The problem is that the file being called is cached on the runner, and if I change it and rerun the workflow, nothing changes and the file is taken from the cache.
I haven't found a way to control this behavior (cache).
Gitea Version
1.25.4
Can you reproduce the bug on the Gitea demo site?
Yes
Log Gist
No response
Screenshots
No response
Git Version
No response
Operating System
No response
How are you running Gitea?
docker
Database
SQLite