github.com/goreleaser/goreleaser@v1.25.1/www/docs/scm/gitea.md (about)

     1  # Gitea
     2  
     3  ## API Token
     4  
     5  GoReleaser requires an API token to deploy the artifacts to Gitea.
     6  You can create one in `Settings | Applications | Generate New Token` page of your Gitea instance.
     7  
     8  This token should be added to the environment variables as `GITEA_TOKEN`.
     9  
    10  Alternatively, you can provide the Gitea token in a file.
    11  GoReleaser will check `~/.config/goreleaser/gitea_token` by default, but you can change that in the `.goreleaser.yaml` file:
    12  
    13  ```yaml
    14  # .goreleaser.yaml
    15  env_files:
    16    gitea_token: ~/.path/to/my/gitea_token
    17  ```
    18  
    19  Note that the environment variable will be used if available, regardless of the
    20  `gitea_token` file.
    21  
    22  ## URLs
    23  
    24  You can use GoReleaser with Gitea by providing its URLs in
    25  the `.goreleaser.yaml` configuration file. This takes a normal string, or a template value.
    26  
    27  ```yaml
    28  # .goreleaser.yaml
    29  gitea_urls:
    30    api: https://gitea.myinstance.com/api/v1
    31    download: https://gitea.myinstance.com
    32    # set to true if you use a self-signed certificate
    33    skip_tls_verify: false
    34  ```