docs: Document the (subtle) differences between GitHub and Forgejo Actions #307

n0toose commented 2023年07月21日 11:42:48 +02:00

We probably should use this thread to document these things too.

We probably should use this thread to document these things too.

chrysn commented 2023年07月21日 11:57:19 +02:00

Differences I encountered, and recommendations I'd make to users encountering them:

• Different default namespace.
  • Recommendation: Point to full URIs, unless it's one of the "common" actions. (Not sure whether GitHub accepts full URIs there; if so, maybe offer workaround).
• Some of the common actions (in GitHub's and Forgejo's "actions" group) are missing. For example, actions/upload-artifact is unavailable. (Is that because there are no artifacts on Codeberg / because they work differently?)
  • Recommendation: Unclear. Maybe at the time this is declared stable, the common actions will be replicated (or, when inapplicable, possibly replaced with a shim action that, in the favor of workflows being reusable across platforms, just warns or prints an error that this doesn't work).
• The token made available inside the action is read-only (whereas GitHub's is read-write by default, with extra API access for closing issues and such)
  • Recommendation: Use SSH deploy keys with write permissions. Setting them up is not trivial (especially if the action goes around cloning into and pushing from different docker images); I plan to make my setup into an action.
    Alternatively, wait for scoped tokens, or even configurable scope for the one already passed in (see forgejo/forgejo#1082).

Differences I encountered, and recommendations I'd make to users encountering them: * Different default namespace. * Recommendation: Point to full URIs, unless it's one of the "common" actions. (Not sure whether GitHub accepts full URIs there; if so, maybe offer workaround). * Some of the common actions (in GitHub's and Forgejo's "actions" group) are missing. For example, actions/upload-artifact is unavailable. (Is that because there are no artifacts on Codeberg / because they work differently?) * Recommendation: Unclear. Maybe at the time this is declared stable, the common actions will be replicated (or, when inapplicable, possibly replaced with a shim action that, in the favor of workflows being reusable across platforms, just warns or prints an error that this doesn't work). * The token made available inside the action is read-only (whereas GitHub's is read-write by default, with extra API access for closing issues and such) * Recommendation: Use SSH deploy keys with write permissions. Setting them up is not trivial (especially if the action goes around cloning into and pushing from different docker images); I plan to make my setup into an action. Alternatively, wait for scoped tokens, or even configurable scope for the one already passed in (see https://codeberg.org/forgejo/forgejo/issues/1082).

mahlzahn commented 2025年09月12日 11:41:24 +02:00

That is implemented now: https://forgejo.org/docs/latest/user/actions/github-actions/

That is implemented now: https://forgejo.org/docs/latest/user/actions/github-actions/