GIT_API_TAGGING defaults to true, which tries to create tags via the
GitHub REST API (api.github.com). On self-hosted Gitea, this fails.
Setting it to false uses git push origin <tag> instead, which works
with the credentials configured by actions/checkout.
Uses anothrNick/github-tag-action (v1.75.0) to bump version and create
a git tag based on #major/#minor/#patch keywords in merge commits.
Runs only on push events to main (i.e. after a PR merge).
Also adds fetch-depth: 0 to checkout so the tag action can see all tags.
Fixes docker/build-push-action SHA: f9a3042 -> f9f3042 (v7.2.0).
Uses anothrNick/github-tag-action (v1.75.0) to bump version and create
a git tag based on #major/#minor/#patch keywords in merge commits.
Runs only on push events to main (i.e. after a PR merge).
Also adds fetch-depth: 0 to checkout so the tag action can see all tags.
Uses anothrNick/github-tag-action (v1.75.0) to bump version and create
a git tag based on #major/#minor/#patch keywords in merge commits.
Runs only on push events to main (i.e. after a PR merge).
Also adds fetch-depth: 0 to checkout so the tag action can see all tags.
This repository builds and publishes a Docker image for [OpenCode](https://opencode.ai), the open source AI coding agent. The image runs OpenCode in headless server mode (`opencode serve`) and is automatically rebuilt and pushed to Docker Hub (`jcabillot/opencode`) every night by a Jenkins pipeline.
This repository builds and publishes a Docker image for [OpenCode](https://opencode.ai), the open source AI coding agent. The image runs OpenCode in headless server mode (`opencode serve`) and is automatically rebuilt and pushed to Docker Hub (`jcabillot/opencode`) every night by a Gitea Actions pipeline.
├── opencode-attach # Helper script for attaching to a running server
├── opencode-attach # Helper script for attaching to a running server
└── README.md # Usage documentation
└── README.md # Usage documentation
```
```
## Dependency management
- **Always pin versions** in the Dockerfile `npm install` command (e.g. `opencode-ai@1.16.2 n2-soul@9.0.9`). Never leave packages unpinned.
- **Update renovate customManagers** when adding, removing, or renaming a dependency tracked in the Dockerfile. Each pinned package must have a corresponding `customManager` entry in `renovate.json` with a regex `matchStrings` pattern that captures the version. If a dependency is added without a renovate entry, Renovatebot will not open automated PRs for it.
- **apt packages** (apt-get install lines in Dockerfile) and **COPY --from** image references are not currently tracked by Renovate. Pinning these manually is acceptable for now but adding renovate managers for them is encouraged.
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.