[PR #431] [MERGED] Update branch deployments #1092

Closed
opened 2026-03-15 15:52:20 +03:00 by kerem · 0 comments
Owner

📋 Pull Request Information

Original PR: https://github.com/flyimg/flyimg/pull/431
Author: @GrantBirki
Created: 3/24/2024
Status: Merged
Merged: 3/25/2024
Merged by: @sadok-f

Base: mainHead: patch-1


📝 Commits (2)

  • feb7a0b Update branch-dev-deploy.yml
  • ad28de9 Merge branch 'main' into patch-1

📊 Changes

1 file changed (+11 additions, -3 deletions)

View changed files

📝 .github/workflows/branch-dev-deploy.yml (+11 -3)

📄 Description

👋 Hey folks! I am the creator and main maintainer for the branch-deploy Action. I saw that you were using it and wanted to bring in some improvements.

I have done the following:

  • Upgraded to v9. It should be safe for you to do so in this project (I checked)
  • Added a more specific if: block to help prevent excess Actions workflows to trigger when folks leave comments on PRs that don't contain .deploy style commands
  • Added an extra permissions statement (only really applies to private repos but its safe to add here)

🔄 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/flyimg/flyimg/pull/431 **Author:** [@GrantBirki](https://github.com/GrantBirki) **Created:** 3/24/2024 **Status:** ✅ Merged **Merged:** 3/25/2024 **Merged by:** [@sadok-f](https://github.com/sadok-f) **Base:** `main` ← **Head:** `patch-1` --- ### 📝 Commits (2) - [`feb7a0b`](https://github.com/flyimg/flyimg/commit/feb7a0be58e3dca1aa12ff6e5a06598a69d55d9a) Update branch-dev-deploy.yml - [`ad28de9`](https://github.com/flyimg/flyimg/commit/ad28de952397e1e2277be3a31a3988f97f5708ba) Merge branch 'main' into patch-1 ### 📊 Changes **1 file changed** (+11 additions, -3 deletions) <details> <summary>View changed files</summary> 📝 `.github/workflows/branch-dev-deploy.yml` (+11 -3) </details> ### 📄 Description 👋 Hey folks! I am the creator and main maintainer for the branch-deploy Action. I saw that you were using it and wanted to bring in some improvements. I have done the following: - Upgraded to `v9`. It should be safe for you to do so in this project (I checked) - Added a more specific `if:` block to help prevent excess Actions workflows to trigger when folks leave comments on PRs that don't contain `.deploy` style commands - Added an extra permissions statement (only really applies to private repos but its safe to add here) --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>
kerem 2026-03-15 15:52:20 +03:00
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/flyimg#1092
No description provided.