starred/panel
1
0
Fork 0
mirror of https://github.com/pelican-dev/panel.git synced 2026-02-24 19:08:53 +03:00
Code Issues 42 Packages Projects Releases 12 Wiki Activity

[PR #1724] [MERGED] Make tests fail-fast & common env #1541

New Issue
Closed
opened 2026-02-04 19:55:37 +03:00 by OVERLORD · 0 comments
OVERLORD commented 2026-02-04 19:55:37 +03:00
Owner
Copy Link

📋 Pull Request Information

Original PR: https://github.com/pelican-dev/panel/pull/1724
Author: @rmartinoscar
Created: 9/20/2025
Status: ✅ Merged
Merged: 9/24/2025
Merged by: @rmartinoscar

Base: main ← Head: chore/tests

📝 Commits (1)

  • 741a7a2 Make tests fail-fast & common env

📊 Changes

4 files changed (+50 additions, -83 deletions)

View changed files

📝 .github/workflows/build.yaml (+1 -1)
📝 .github/workflows/ci.yaml (+48 -79)
📝 .github/workflows/docker-publish.yml (+0 -2)
📝 .github/workflows/lint.yaml (+1 -1)

📄 Description

We don't need to bloat github workers with full matrix tests when either of them failed.
Also used a common env and overwritting required keys instead of duplicating them.

🔄 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/1724 **Author:** [@rmartinoscar](https://github.com/rmartinoscar) **Created:** 9/20/2025 **Status:** ✅ Merged **Merged:** 9/24/2025 **Merged by:** [@rmartinoscar](https://github.com/rmartinoscar) **Base:** `main` ← **Head:** `chore/tests` --- ### 📝 Commits (1) - [`741a7a2`](https://github.com/pelican-dev/panel/commit/741a7a2da0cb9b8adf02f19b027026b0becab4c0) Make tests fail-fast & common env ### 📊 Changes **4 files changed** (+50 additions, -83 deletions) <details> <summary>View changed files</summary> 📝 `.github/workflows/build.yaml` (+1 -1) 📝 `.github/workflows/ci.yaml` (+48 -79) 📝 `.github/workflows/docker-publish.yml` (+0 -2) 📝 `.github/workflows/lint.yaml` (+1 -1) </details> ### 📄 Description We don't need to bloat github workers with full matrix tests when either of them failed. Also used a common env and overwritting required keys instead of duplicating them. --- <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-04 19:55:37 +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#1541
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?