mirror of
https://github.com/nektos/act.git
synced 2026-04-26 01:15:51 +03:00
[PR #1148] [MERGED] Remove the correct Volume #1805
Labels
No labels
area/action
area/cli
area/docs
area/image
area/runner
area/workflow
backlog
confirmed/not-planned
kind/bug
kind/discussion
kind/external
kind/feature-request
kind/question
meta/duplicate
meta/invalid
meta/need-more-info
meta/resolved
meta/wontfix
meta/workaround
needs-work
pull-request
review/not-planned
size/M
size/XL
size/XXL
stale
stale-exempt
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/act#1805
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/nektos/act/pull/1148
Author: @ChristopherHX
Created: 5/4/2022
Status: ✅ Merged
Merged: 5/11/2022
Merged by: @mergify[bot]
Base:
master← Head:fix-remove-correct-volume📝 Commits (2)
666a78bRemove the correct Volumebb82409Merge branch 'master' into fix-remove-correct-volume📊 Changes
1 file changed (+1 additions, -1 deletions)
View changed files
📝
pkg/runner/run_context.go(+1 -1)📄 Description
I have a lot of stale act-....-env volumes
I have the feeling, this can cause bugs if we have a job id collisions
🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.