forgejo/runner

Watch

Fork 114

cherry-picking ACT/runner commits #835

New issue

Open

opened 2025-08-10 16:49:39 +00:00 by earl-warren · 4 comments

earl-warren commented

2025-08-10 16:49:39 +00:00

Contributor

When new commits are found:

Add a comment that shows which they are and what are those worth looking at
Update this description to the new head of each repo

- Nektos ACT - https://github.com/nektos/act/compare/e374ef962fc15812c175ff9ad6c33d77b8684e05...master - Gitea ACT - https://gitea.com/gitea/act/compare/91852faf934e3436fe427d70017b9a630d1421df...main - act_runner - https://gitea.com/gitea/act_runner/compare/8920c4a170603dc8f23e9e0d4ba0a9de13cd5f94...main --- See also [the previous issue related to collecting and porting Nektos & Gitea ACT commits](https://code.forgejo.org/forgejo/runner/issues/678), completed August 2025. --- When new commits are found: - Add a comment that shows which they are and what are those worth looking at - Update this description to the new head of each repo

earl-warren added the

Kind/Chore

label

2025-08-10 16:49:39 +00:00

earl-warren referenced this issue

2025-08-10 16:51:50 +00:00

cherry-picking Nektos Act commits #678

earl-warren pinned this

2025-08-10 16:52:11 +00:00

earl-warren changed title from ~~cherry-picking ACT commits~~ to cherry-picking ACT/runner commits

2025-08-10 16:57:43 +00:00

achyrva referenced this issue

2025-08-20 11:58:59 +00:00

WIP: fix: add missing service container health check (#2354) #892

earl-warren commented

2025-08-26 06:29:19 +00:00

Author

Contributor

Nektos ACT - github.com/nektos/act@a78b3f305a...e374ef962f
Gitea ACT - gitea.com/gitea/act@39509e9ad0...91852faf93
act_runner - gitea.com/gitea/act_runner@53329c46ff...8920c4a170
💡fix: step container workdir and mounts
💡fix: matrix expansion logic
💡Timeout to wait for and optionally require docker always - there are no tests

- Nektos ACT - https://github.com/nektos/act/compare/a78b3f305a43a143283fb7d02f3b24df1577ce3e...e374ef962fc15812c175ff9ad6c33d77b8684e05 - Gitea ACT - https://gitea.com/gitea/act/compare/39509e9ad05c7a4a79c4b48e8a97f8203db70dbf...91852faf934e3436fe427d70017b9a630d1421df - act_runner - https://gitea.com/gitea/act_runner/compare/53329c46ff29922cea0d02a0d52a039308f4bd99...8920c4a170603dc8f23e9e0d4ba0a9de13cd5f94 - 💡[fix: step container workdir and mounts](https://github.com/nektos/act/commit/2dea26ba3a258510b21a857e40643d253e024080) - 💡[fix: matrix expansion logic](https://github.com/nektos/act/commit/e374ef962fc15812c175ff9ad6c33d77b8684e05) - 💡[Timeout to wait for and optionally require docker always](https://gitea.com/gitea/act_runner/pulls/741) - there are no tests

kaechele commented

2026-03-27 19:01:12 +00:00

It would be great if this commit could be picked up: gitea.com/gitea/act_runner@9933ea0d92

I'm hoping that this will fix bind mounting for actions that build a docker container and then have it operate on sources that were checked out into the workspace previously. Specifically github.com/esphome/build-action@f0a331817f/action.yml (L76)

It would be great if this commit could be picked up: https://gitea.com/gitea/act_runner/commit/9933ea0d9270c9c9e687aed7953a7a95e0c5c4bd I'm hoping that this will fix bind mounting for actions that build a docker container and then have it operate on sources that were checked out into the workspace previously. Specifically https://github.com/esphome/build-action/blob/f0a331817f5535854a10a42621b6a8b7ebe95c4c/action.yml#L76

aahlenst commented

2026-03-27 19:08:05 +00:00

Member

@kaechele It cannot be picked up because it has been made with the help of a coding agent. That would be a violation of the Forgejo AI Agreement. It also lacks tests. If you want that capability, please file a request on https://code.forgejo.org/forgejo/forgejo-actions-feature-requests/issues.

@kaechele It cannot be picked up because it has been made with the help of a coding agent. That would be a violation of the [Forgejo AI Agreement](https://codeberg.org/forgejo/governance/src/commit/19ef60442456b92156a242ad1bbc1bcda98bef3b/AIAgreement.md). It also lacks tests. If you want that capability, please file a request on https://code.forgejo.org/forgejo/forgejo-actions-feature-requests/issues.

kaechele commented

2026-03-27 19:40:23 +00:00

Understood. Thanks for the response! I will create a feature request accordingly.

No milestone

No assignees

3 participants

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

forgejo/runner#835

No description provided.

Rows
Columns