starred/panel-pelican-dev
1
0
Fork 0
mirror of https://github.com/pelican-dev/panel.git synced 2026-05-04 18:00:48 +03:00
Code Issues 41 Packages Projects Releases 10 Wiki Activity

[PR #662] [MERGED] Adding fix for forks to use a variable for Docker image reference instead of hard String #885

New Issue
Closed
opened 2026-02-05 17:57:29 +03:00 by OVERLORD · 0 comments
OVERLORD commented 2026-02-05 17:57:29 +03:00
Owner
Copy Link

📋 Pull Request Information

Original PR: https://github.com/pelican-dev/panel/pull/662
Author: @BlockyBlockling
Created: 10/24/2024
Status: ✅ Merged
Merged: 10/27/2024
Merged by: @parkervcp

Base: main ← Head: docker-workflow-rework

📝 Commits (1)

  • 86e8a63 Update docker-publish.yml

📊 Changes

1 file changed (+5 additions, -1 deletions)

View changed files

📝 .github/workflows/docker-publish.yml (+5 -1)

📄 Description

Adding fix for forks to use a variable for Docker image reference instead of hard String

Source of information:
https://docs.github.com/en/actions/use-cases-and-examples/publishing-packages/publishing-docker-images

This is just changing the docker image publish to publish an image to the repository the workflow is running at.
It allows fork of the repository to publish their own images to the accourding fork registry. Instead that every single workflow tries to push into the pelican-dev/panel repo and get a not authorized error.

🔄 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/pelican-dev/panel/pull/662 **Author:** [@BlockyBlockling](https://github.com/BlockyBlockling) **Created:** 10/24/2024 **Status:** ✅ Merged **Merged:** 10/27/2024 **Merged by:** [@parkervcp](https://github.com/parkervcp) **Base:** `main` ← **Head:** `docker-workflow-rework` --- ### 📝 Commits (1) - [`86e8a63`](https://github.com/pelican-dev/panel/commit/86e8a6371ea8d96833e1e9e30db82390d824182f) Update docker-publish.yml ### 📊 Changes **1 file changed** (+5 additions, -1 deletions) <details> <summary>View changed files</summary> 📝 `.github/workflows/docker-publish.yml` (+5 -1) </details> ### 📄 Description Adding fix for forks to use a variable for Docker image reference instead of hard String Source of information: https://docs.github.com/en/actions/use-cases-and-examples/publishing-packages/publishing-docker-images This is just changing the docker image publish to publish an image to the repository the workflow is running at. It allows fork of the repository to publish their own images to the accourding fork registry. Instead that every single workflow tries to push into the pelican-dev/panel repo and get a not authorized error. --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>
OVERLORD added the pull-request label 2026-02-05 17:57:29 +03:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
not confirmed
pull-request
Mirrored from GitHub Pull Request
 👑 sponsor
💰 fund
🔴 hard
🟡 medium
🟡 medium
🟡 medium
🟢 easy
🟢 easy
🟢 easy
No Label pull-request
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
OVERLORD
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/panel-pelican-dev#885
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?