[GH-ISSUE #261] Running workflows locally on Act behave differently than running on Github #178

New issue

Closed

opened 2026-03-01 21:40:57 +03:00 by kerem · 2 comments

kerem commented

2026-03-01 21:40:57 +03:00

Owner

Originally created by @shaal on GitHub (May 29, 2020).
Original GitHub issue: https://github.com/nektos/act/issues/261

(Thank you for the explanation in https://github.com/nektos/act/issues/197#issuecomment-628223869)

I tested this workflow:
https://github.com/palantirnet/drupal-rector/blob/master/.github/workflows/local_package_functional_tests.yml

And found that when running the workflow in Github, every run: section inside 1 job, "forgets" the location changes that were done in a previous run.
For an example:
cd drupal in https://github.com/palantirnet/drupal-rector/blob/master/.github/workflows/packagist_package_run_rector.yml#L32
needs to run again in https://github.com/palantirnet/drupal-rector/blob/master/.github/workflows/packagist_package_run_rector.yml#L39
and run again in every run: after that.

But when I run the same script locally in act (using act -P ubuntu-latest=shivammathur/node:latest)
It does not "forget" the location in a previous run, which messes up the special setup needed for that test.

Originally created by @shaal on GitHub (May 29, 2020). Original GitHub issue: https://github.com/nektos/act/issues/261 (Thank you for the explanation in https://github.com/nektos/act/issues/197#issuecomment-628223869) I tested this workflow: https://github.com/palantirnet/drupal-rector/blob/master/.github/workflows/local_package_functional_tests.yml And found that when running the workflow in Github, every `run:` section inside 1 job, "forgets" the location changes that were done in a previous run. For an example: `cd drupal` in https://github.com/palantirnet/drupal-rector/blob/master/.github/workflows/packagist_package_run_rector.yml#L32 needs to run again in https://github.com/palantirnet/drupal-rector/blob/master/.github/workflows/packagist_package_run_rector.yml#L39 and run again in every `run:` after that. But when I run the same script locally in `act` (using `act -P ubuntu-latest=shivammathur/node:latest`) It does not "forget" the location in a previous run, which messes up the special setup needed for that test.

kerem

2026-03-01 21:40:57 +03:00

closed this issue
added the
stale

area/action

kind/bug
labels

kerem commented

2026-03-01 21:40:58 +03:00

Author

Owner

@shaal commented on GitHub (Jul 5, 2020):

How can I resolve this problem?

@shaal commented on GitHub (Jul 5, 2020): How can I resolve this problem?

kerem commented

2026-03-01 21:40:58 +03:00

Author

Owner

@github-actions[bot] commented on GitHub (Sep 4, 2020):

Issue is stale and will be closed in 7 days unless there is new activity

@github-actions[bot] commented on GitHub (Sep 4, 2020): Issue is stale and will be closed in 7 days unless there is new activity

No milestone

No project

No assignees

1 participant

Notifications

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference

starred/act#178

No description provided.

Rows
Columns