mirror of
https://github.com/ramsayleung/rspotify.git
synced 2026-04-25 23:45:52 +03:00
[PR #463] [MERGED] [Fix] Fix the filter of GitHub Action on event #473
Labels
No labels
Stale
bug
discussion
enhancement
good first issue
good first issue
help wanted
pull-request
question
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/rspotify#473
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
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?
📋 Pull Request Information
Original PR: https://github.com/ramsayleung/rspotify/pull/463
Author: @ramsayleung
Created: 3/8/2024
Status: ✅ Merged
Merged: 3/8/2024
Merged by: @ramsayleung
Base:
master← Head:ramsay/fix-github-action-on-filter📝 Commits (1)
7cbf2db[fix] Fix the filter of on event, only trigger the workflow when new tag named📊 Changes
1 file changed (+1 additions, -1 deletions)
View changed files
📝
.github/workflows/publish.yaml(+1 -1)📄 Description
Description
Fix the filter of GitHub Action on event
Motivation and Context
The
onsection specifies the events that trigger workflow, what I expect is the workflow only get triggered when new tag namev*is created(e.g. new version is published).However, the current configuration will trigger the workflow not only when a new tag is created but also when any other type of creation event occurs(such as creating a new branch)
Fixing it by enclosing the tag pattern
'v*'in single quotes, it should explicitly specfy that the workflow should trigger only when a new tg matching that pattern is created.Dependencies
None
Type of change
Please delete options that are not relevant.
How has this been tested?
This PR shoudn't trigger the
Publish CreateworkflowIs this change properly documented?
It's unnecessary.
🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.