github-starred/vikunja
2
0
Fork 0
mirror of https://github.com/go-vikunja/vikunja.git synced 2026-07-15 22:32:29 -05:00
Code Issues 690 Packages Projects Releases 11 Wiki Activity

[PR #1810] [MERGED] feat: add PR Docker image builds for x86_64 #5241

New Issue
Closed
opened 2026-04-16 13:31:39 -05:00 by GiteaMirror · 0 comments
GiteaMirror commented 2026-04-16 13:31:39 -05:00
Owner
Copy Link

📋 Pull Request Information

Original PR: https://github.com/go-vikunja/vikunja/pull/1810
Author: @Copilot
Created: 11/12/2025
Status: ✅ Merged
Merged: 11/12/2025
Merged by: @kolaente

Base: main ← Head: copilot/build-docker-image-x86

📝 Commits (3)

  • c2a8c34 Initial plan
  • 8ee6822 feat: add PR docker build workflow
  • f1c9139 feat: add SHA tag to PR Docker images

📊 Changes

1 file changed (+47 additions, -0 deletions)

View changed files

➕ .github/workflows/pr-docker.yml (+47 -0)

📄 Description

Build and push Docker images to GHCR for every PR to enable testing without waiting for CI.

Changes

  • New workflow .github/workflows/pr-docker.yml
    • Triggers on pull_request events
    • Builds linux/amd64 only (vs multi-arch in release)
    • Pushes to ghcr.io/go-vikunja/vikunja only (not Docker Hub)
    • Tags with both pr-<number> and sha-<commit_hash> for easy identification
    • Runs immediately without waiting for test jobs
    • Uses GitHub Actions cache for faster builds

Usage

# Pull by PR number
docker pull ghcr.io/go-vikunja/vikunja:pr-123

# Or pull by commit SHA
docker pull ghcr.io/go-vikunja/vikunja:sha-<commit_hash>

# Run the container
docker run -p 3456:3456 ghcr.io/go-vikunja/vikunja:pr-123
Original prompt

for each pr, build a docker image and push it to ghcr (only). Similar to the release docker build, but only for the x86 arch and only push to ghcr. The build should start right away without waiting for any of the tests

💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.

🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.

## 📋 Pull Request Information **Original PR:** https://github.com/go-vikunja/vikunja/pull/1810 **Author:** [@Copilot](https://github.com/apps/copilot-swe-agent) **Created:** 11/12/2025 **Status:** ✅ Merged **Merged:** 11/12/2025 **Merged by:** [@kolaente](https://github.com/kolaente) **Base:** `main` ← **Head:** `copilot/build-docker-image-x86` --- ### 📝 Commits (3) - [`c2a8c34`](https://github.com/go-vikunja/vikunja/commit/c2a8c34750af163d7a006e7123026e9f2a23ff09) Initial plan - [`8ee6822`](https://github.com/go-vikunja/vikunja/commit/8ee682215dd6c4ef38764cc5ea7c1d3f2ef5037b) feat: add PR docker build workflow - [`f1c9139`](https://github.com/go-vikunja/vikunja/commit/f1c91398a4959b1f973d2dc648235b6156c8d429) feat: add SHA tag to PR Docker images ### 📊 Changes **1 file changed** (+47 additions, -0 deletions) <details> <summary>View changed files</summary> ➕ `.github/workflows/pr-docker.yml` (+47 -0) </details> ### 📄 Description Build and push Docker images to GHCR for every PR to enable testing without waiting for CI. ## Changes - **New workflow** `.github/workflows/pr-docker.yml` - Triggers on `pull_request` events - Builds `linux/amd64` only (vs multi-arch in release) - Pushes to `ghcr.io/go-vikunja/vikunja` only (not Docker Hub) - Tags with both `pr-<number>` and `sha-<commit_hash>` for easy identification - Runs immediately without waiting for test jobs - Uses GitHub Actions cache for faster builds ## Usage ```bash # Pull by PR number docker pull ghcr.io/go-vikunja/vikunja:pr-123 # Or pull by commit SHA docker pull ghcr.io/go-vikunja/vikunja:sha-<commit_hash> # Run the container docker run -p 3456:3456 ghcr.io/go-vikunja/vikunja:pr-123 ``` <!-- START COPILOT CODING AGENT SUFFIX --> <details> <summary>Original prompt</summary> > for each pr, build a docker image and push it to ghcr (only). Similar to the release docker build, but only for the x86 arch and only push to ghcr. The build should start right away without waiting for any of the tests </details> <!-- START COPILOT CODING AGENT TIPS --> --- 💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more [Copilot coding agent tips](https://gh.io/copilot-coding-agent-tips) in the docs. --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>
GiteaMirror added the pull-request label 2026-04-16 13:31:39 -05:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
area/api
area/attachments
area/auth
area/avatars
area/backup-restore
area/caldav
area/calendar-view
area/comments
area/config
area/database
area/desktop
area/docker
area/email
area/favorites
area/filters
area/frontend
area/gantt
area/i18n
area/import-export
area/internal-code
area/kanban
area/labels
area/list-view
area/mobile
area/notifications
area/permissions
area/projects
area/pwa
area/recurring-tasks
area/reminders
area/search
area/shortcuts
area/subtasks
area/sync
area/table-view
area/task-editor
area/task-metadata
area/task-relations
area/teams
area/theming
area/time-tracking
area/typesense
area/views
area/webhooks
bug
changes requested
concern/accessibility
concern/performance
concern/regression
concern/ux
confirmed
db/mysql
dependencies
enhancement
good first issue
help wanted
integration/inbound
integration/outbound
kind/bug
kind/feature
needs reproduction
pull-request
Mirrored from GitHub Pull Request
 question
security
support
upstream issue
waiting for reply
wontfix
No Label pull-request
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
GiteaMirror ninjasurge
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/vikunja#5241
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?