{{ message }}
[ci] Cleanup of unused and broken GitHub Actions#29728
Merged
iBotPeaches merged 5 commits intofastlane:masterfrom Nov 29, 2025
Merged
[ci] Cleanup of unused and broken GitHub Actions#29728iBotPeaches merged 5 commits intofastlane:masterfrom
iBotPeaches merged 5 commits intofastlane:masterfrom
Conversation
This was referenced Oct 17, 2025
Closed
iBotPeaches
force-pushed
the
action-cleanup
branch
from
723dc48 to
bfda912
Compare
# Conflicts: # .github/workflows/create_tag_on_bump_merge.yml # .github/workflows/deploy_to_rubygems.yml
iBotPeaches
force-pushed
the
action-cleanup
branch
from
bfda912 to
717a29c
Compare
Collaborator
Member
Author
On Part 2 of release towards the end it does a "gem push" to RubyGems and GHA - Line 399 in 8d706b4 So automatic after a manual kick off of Part 2 workflows. |
lacostej
approved these changes
Nov 28, 2025
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Motivation and Context
As you click on the various workflows - this is what you find:
create tag on bump merge- this is hardcoded to ONLY release 221. It never really fires anymore except to run and instantly fail because its not version 221, the existing Step 1 & Step 2 automation jobs handle tag creation.
deploy to rubygems - much like last - never fired - 0 executions logged. Its logic was moved into Step 2.
process release - this SHOULD fire, but since GitHub Action won't dispatch an event if it caused the action. This never fired.
Description
I removed any action that has never fired and looks unneeded. I fixed the Process Release action to hook onto the Step 2 workflow so it should fire once that is completed.
Testing Steps
Tough to test GitHub Actions with how much is wired up via keys n such. You can review the removals to see the job has never been fired. You can review the fixed job and since it had never fired previously - it should be fine. It will fail however once it works because the GitHub Actions repo has decayed.