feat: publish Docker image to GHCR on each release
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 292
- Forks
- 136
- Avg merge
- 19m
- Merged PRs (30d)
- 1
Description
## Description
Automate Docker image builds and publish them to GitHub Container Registry (GHCR) on each tagged release.
## Current state
The project has a `Dockerfile` that builds a production image using `node:20-alpine`, but images are only built locally. Users must clone the repo and build manually.
## Proposal
Add a GitHub Actions workflow that:
1. Triggers on tag push (`v*`)
2. Builds the Docker image using the existing `Dockerfile`
3. Pushes to `ghcr.io/lnp2pbot/bot:vX.Y.Z` and `ghcr.io/lnp2pbot/bot:latest`
4. Uses multi-platform builds (amd64 + arm64) for broader deployment support
## Benefits
- Operators can pull pre-built images instead of building from source
- Consistent, reproducible deployments
- Version-pinned images for production stability
- Enables easier Docker Compose / Kubernetes deployments
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reading the existing Dockerfile and then inspect the repository’s GitHub Actions conventions, if any. The work is done when a v* tag builds the image for amd64 and arm64 and publishes both the versioned tag and latest to ghcr.io/lnp2pbot/bot.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, github-actions
- Domain
- ci-cd, devops, release
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 68/100