Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Allow Update Gem Version Artifacts workflow to trigger CI build. #228

Merged
merged 1 commit into from
Feb 25, 2025

Conversation

myronmarston
Copy link
Collaborator

Both #225 and #226 received updated commits from the Update Gem Version Artifacts workflow, but the CI build did not run in either case. This should fix it so that it runs.

@CLAassistant
Copy link

CLA assistant check
Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.
You have signed the CLA already but the status is still pending? Let us recheck it.

Both #225 and #226 received updated commits from the `Update Gem Version
Artifacts` workflow, but the CI build did not run in either case. This
should fix it so that it runs.
@myronmarston myronmarston force-pushed the myron/allow-chained-workflow branch from 8f4a8bf to 2cf9f4c Compare February 25, 2025 01:09
@myronmarston myronmarston merged commit 91fcfae into main Feb 25, 2025
15 of 17 checks passed
@myronmarston myronmarston deleted the myron/allow-chained-workflow branch February 25, 2025 01:10
myronmarston added a commit that referenced this pull request Feb 25, 2025
I merged #228 too quickly--the `ci.yaml` template needs to be updated as well.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants