langgenius/dify-plugin-sdks
1
0
Fork 0
mirror of https://github.com/langgenius/dify-plugin-sdks.git synced 2026-07-22 02:15:22 -04:00
Code Issues 58 Packages Projects Releases 10 Wiki Activity

[PR #102] [CLOSED] chore: Limit CI pipeline to trigger only on main branch pushes #146

New Issue
Closed
opened 2026-02-15 21:15:58 -05:00 by yindo · 0 comments
yindo commented 2026-02-15 21:15:58 -05:00
Owner
Copy Link
Copy Source

📋 Pull Request Information

Original PR: https://github.com/langgenius/dify-plugin-sdks/pull/102
Author: @QuantumGhost
Created: 4/16/2025
Status: ❌ Closed

Base: main ← Head: main

📝 Commits (1)

  • 56688ee chore: Limit CI pipeline to trigger only on main branch pushes

📊 Changes

2 files changed (+4 additions, -0 deletions)

View changed files

📝 .github/workflows/mega-linter.yaml (+2 -0)
📝 .github/workflows/pull-request.yaml (+2 -0)

📄 Description

Previously, the Pull Request and the MegaLinter pipelines were triggered on pushes to any branch, including feature branches and other temporary branches. This behavior unnecessarily consumed CI execution quotas.

This change restricts the triggers for these pipelines, ensuring they only execute on pushes to the main branch.

🔄 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/langgenius/dify-plugin-sdks/pull/102 **Author:** [@QuantumGhost](https://github.com/QuantumGhost) **Created:** 4/16/2025 **Status:** ❌ Closed **Base:** `main` ← **Head:** `main` --- ### 📝 Commits (1) - [`56688ee`](https://github.com/langgenius/dify-plugin-sdks/commit/56688ee1cd259745bf34eb83e236e126e5e33555) chore: Limit CI pipeline to trigger only on main branch pushes ### 📊 Changes **2 files changed** (+4 additions, -0 deletions) <details> <summary>View changed files</summary> 📝 `.github/workflows/mega-linter.yaml` (+2 -0) 📝 `.github/workflows/pull-request.yaml` (+2 -0) </details> ### 📄 Description Previously, the `Pull Request` and the `MegaLinter` pipelines were triggered on pushes to any branch, including feature branches and other temporary branches. This behavior unnecessarily consumed CI execution quotas. This change restricts the triggers for these pipelines, ensuring they only execute on pushes to the `main` branch. --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>
yindo added the pull-request label 2026-02-15 21:15:58 -05:00
yindo closed this issue 2026-02-15 21:15:58 -05:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
bug
documentation
enhancement
pull-request
Mirrored from GitHub Pull Request
 question
No Label pull-request
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
yindo
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: langgenius/dify-plugin-sdks#146
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?