Skip to content

SHREK-362: switch from semaphore to gha - #13

Merged
RyanNielson merged 1 commit into
masterfrom
SHREK-362-migrate-from-semaphore-to-gha
Jan 9, 2026
Merged

SHREK-362: switch from semaphore to gha#13
RyanNielson merged 1 commit into
masterfrom
SHREK-362-migrate-from-semaphore-to-gha

Conversation

@RyanNielson

Copy link
Copy Markdown
Contributor

Ticket

Just closing off a ticket in our backlog. This switches the gem to use gha instead of semaphore for CICD. It should basically be a direct copy of the process Semaphore carries out as far as I can tell. This project is rarely updated, but I figured it was a good idea to get this small change out in case we have to make future changes.

Copilot AI left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

This PR migrates the CI/CD pipeline from Semaphore to GitHub Actions. The change removes the Semaphore configuration and replaces it with a GitHub Actions workflow that runs the same test suite and linting checks.

Key changes:

  • Removed .semaphore/semaphore.yml containing the Semaphore CI configuration
  • Added .github/workflows/checks.yml with a GitHub Actions workflow
  • Switched from parallel job execution to sequential execution of tests and linting

Reviewed changes

Copilot reviewed 2 out of 2 changed files in this pull request and generated 4 comments.

File Description
.semaphore/semaphore.yml Removed Semaphore CI configuration that ran parallel RSpec and Rubocop jobs
.github/workflows/checks.yml Added GitHub Actions workflow to run tests and linting on Ruby 2.6

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

Comment thread .github/workflows/checks.yml Outdated
Comment thread .github/workflows/checks.yml
Comment thread .github/workflows/checks.yml Outdated
Comment thread .github/workflows/checks.yml
@RyanNielson
RyanNielson force-pushed the SHREK-362-migrate-from-semaphore-to-gha branch from dceccfa to fb0e32a Compare January 8, 2026 17:02
@RyanNielson
RyanNielson requested a review from Copilot January 8, 2026 17:08

Copilot AI left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

Copilot reviewed 2 out of 2 changed files in this pull request and generated no new comments.


💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

@RyanNielson
RyanNielson force-pushed the SHREK-362-migrate-from-semaphore-to-gha branch from fb0e32a to 484c1bd Compare January 8, 2026 20:24
@RyanNielson
RyanNielson force-pushed the SHREK-362-migrate-from-semaphore-to-gha branch from 484c1bd to f044b9d Compare January 8, 2026 20:25

jobs:
checks:
runs-on: ubuntu-latest

@RyanNielson RyanNielson Jan 8, 2026

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@seanvm @joseasouza I'm using one of GitHub's runners because we can't use our own self-hosted runners in public repositories due to security concerns. No a problem though, ubuntu-latest is free. Speaking of which, do we need this repo to be public, and what would the consequences of making it private be?

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think it needs to public so bundle can pull the gem directly from the repo?
Another option would be to publish a version of this to a private gem repo

@joseasouza joseasouza left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think if it

@RyanNielson
RyanNielson merged commit df88ba9 into master Jan 9, 2026
2 checks passed
@RyanNielson
RyanNielson deleted the SHREK-362-migrate-from-semaphore-to-gha branch January 9, 2026 14:57
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