self-hosting/workflows
self-hosting/workflows
5
0
Fork 0
Code Issues 2 Pull requests Projects Activity Actions

Use explicit jobs to control runs-on #19

Merged
2franix merged 1 commit from explicit_runs_on into main 2025-02-23 22:11:29 +01:00
Conversation 0 Commits 1 Files changed 1 +17 -4
2franix commented 2025-02-23 22:09:44 +01:00
Owner
Copy link

Controlling runs-on via inputs does not seem to work reliably. It looks like the choice of a runner is made no matter what the input is.

Let's create three explicit jobs to represent the three values for this property.

Controlling `runs-on` via inputs does not seem to work reliably. It looks like the choice of a runner is made no matter what the input is. Let's create three explicit jobs to represent the three values for this property.
Use explicit jobs to control runs-on
All checks were successful
CI / Lint and format files (pull_request) Successful in 37s
Details
6d2bb73214
2franix deleted branch explicit_runs_on 2025-02-23 22:11:30 +01:00
2franix referenced this pull request from a commit 2025-02-23 22:13:53 +01:00
Revert #18 and #17 (#19)
2franix referenced this pull request from a commit 2025-02-23 22:27:13 +01:00
Revert #20 and #19 (#21)
Sign in to join this conversation.
Reviewers
No reviewers
Labels
Clear labels
No items
No labels
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
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: self-hosting/workflows#19
No description provided.
Delete branch "explicit_runs_on"

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?