An action to support publishing generic packages to Gitea. More: https://docs.gitea.com/usage/packages/generic#publish-a-package
  • JavaScript 100%
Find a file
2025-12-30 08:08:42 -05:00
.github/workflows Initialize first version 2024-01-17 19:33:16 +08:00
dist Forgejo 2025-12-30 08:08:42 -05:00
.gitignore Initialize first version 2024-01-17 19:33:16 +08:00
.npmrc Initialize first version 2024-01-17 19:33:16 +08:00
action.yml Forgejo 2025-12-30 08:08:42 -05:00
LICENSE Initialize first version 2024-01-17 19:33:16 +08:00
main.js Forgejo 2025-12-30 08:08:42 -05:00
package-lock.json Forgejo 2025-12-30 08:08:42 -05:00
package.json Forgejo 2025-12-30 08:08:42 -05:00
README.md Forgejo 2025-12-30 08:08:42 -05:00

Forgejo publish generic packages action

An action to support publishing generic packages to Forgejo.

Inputs

The following are optional as step.with keys

Name Type Optional Description
api_url String True The base gitea API url. Defaults to github.api_url
owner String True Assign an owner to this generic package. Defaults to github.repository_owner
package_name String True Gives the generic package a custom name. Defaults to github.event.repository.name
package_version String True Gives a generic package version. Defaults to github.ref_name
files String false Newline-delimited list of path globs for generic package files to upload
token String false The Gitea personal access token
override String false Override (delete and then create) if package with same name + version exists. Defaults to false

Example usage

uses: VAllens/gitea-publish-generic-packages@v1
env:
  NODE_OPTIONS: '--experimental-fetch' # if nodejs < 18
with:
  files: |-
    bin/**

If you want to ignore ssl verify error, you can set env NODE_TLS_REJECT_UNAUTHORIZED=false

References