My understanding is that the act runner we're using is built for supporting github actions first and gitea/forgejo add variables on top. So, it has worked in testing on local and remote runners.
My understanding is that the act runner we're using is built for supporting github actions first and gitea/forgejo add variables on top. So, it has worked in testing on local and remote runners.
@Brooke LGTM overall - do you think there is an easy fix to the the registry push issues? If not, I'm fine merging this while we figure that out.
Not that I'm aware, but I also didn't independently replicate any push issues, the runner seemed to be able to handle it fine. Unless I'm thinking of something else.
> @Brooke LGTM overall - do you think there is an easy fix to the the registry push issues? If not, I'm fine merging this while we figure that out.
Not that I'm aware, but I also didn't independently replicate any push issues, the runner seemed to be able to handle it fine. Unless I'm thinking of something else.
sixsmith
marked the pull request as ready for review 2026-08-27 11:36:10 +00:00
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Looks good overall with some comments. Thanks for working on this!
@@ -0,0 +17,4 @@- name: Get short commit SHAid: varsrun: |calculatedSha=$(git rev-parse --short ${{ github.sha }})Is
github.shasupposed to be available in this context?@@ -0,0 +27,4 @@elseTAG="${{ gitea.ref_name }}"fiecho "RELEASE_TAG=$TAG" >> $GITHUB_ENVSame here as above, is
$GITHUB_ENVgoing to setenv.RELEASE_TAGin a non-GitHub context?My understanding is that the act runner we're using is built for supporting github actions first and gitea/forgejo add variables on top. So, it has worked in testing on local and remote runners.
@Brooke LGTM overall - do you think there is an easy fix to the the registry push issues? If not, I'm fine merging this while we figure that out.
Not that I'm aware, but I also didn't independently replicate any push issues, the runner seemed to be able to handle it fine. Unless I'm thinking of something else.