Skip to content

Comments

Fix CI config by ensuring deployment unset before installing dependencies#69

Closed
MSD118 wants to merge 2 commits intomasterfrom
masood/fix-ci-check-failing-at-set-ruby
Closed

Fix CI config by ensuring deployment unset before installing dependencies#69
MSD118 wants to merge 2 commits intomasterfrom
masood/fix-ci-check-failing-at-set-ruby

Conversation

@MSD118
Copy link

@MSD118 MSD118 commented Feb 16, 2026

This pull request updates the GitHub Actions workflows for both Brakeman and CI jobs to improve dependency installation reliability. The main change is replacing the use of bundler-cache: true with explicit steps to unset the bundler deployment mode and manually install dependencies.

Dependency installation process updates:

  • Removed bundler-cache: true and added steps to unset the bundler deployment configuration and run bundle install manually in both .github/workflows/brakeman.yml and .github/workflows/ci.yml. This helps avoid issues with cached gems and deployment-specific bundler settings. [1] [2]

…loyment unset before installing dependencies
Copilot AI review requested due to automatic review settings February 16, 2026 08:05
Copy link

Copilot AI left a comment

Choose a reason for hiding this comment

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

Pull request overview

Updates GitHub Actions Ruby workflows to avoid Bundler “deployment” mode interfering with dependency installation by explicitly unsetting it and running bundle install manually.

Changes:

  • Disabled ruby/setup-ruby’s bundler-cache: true behavior in CI and Brakeman workflows.
  • Added steps to bundle config unset deployment and then run bundle install.

Reviewed changes

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

File Description
.github/workflows/ci.yml Replaces bundler-cache with explicit Bundler config unset + manual bundle install before running specs.
.github/workflows/brakeman.yml Replaces bundler-cache with explicit Bundler config unset + manual bundle install before installing/running Brakeman.

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

bundler-cache: true
# bundler-cache: true

- name: unset deployment
Copy link

Copilot AI Feb 16, 2026

Choose a reason for hiding this comment

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

Step names in this workflow are capitalized (e.g., "Set up Ruby…", "Install dependencies"), but this new step is not. Rename it to match the existing naming style for consistency and readability.

Suggested change
- name: unset deployment
- name: Unset deployment

Copilot uses AI. Check for mistakes.
Comment on lines 17 to 18
# bundler-cache: true

Copy link

Copilot AI Feb 16, 2026

Choose a reason for hiding this comment

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

There is trailing whitespace on these lines (after the commented bundler-cache line and on the blank line). Consider removing it to avoid lint noise and keep diffs clean.

Suggested change
# bundler-cache: true
# bundler-cache: true

Copilot uses AI. Check for mistakes.
Comment on lines 23 to 27
- name: unset deployment
run: bundle config unset deployment

- name: Install dependencies
run: bundle install
Copy link

Copilot AI Feb 16, 2026

Choose a reason for hiding this comment

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

Gemfile.lock pins Bundler via BUNDLED WITH 2.2.29, but this workflow no longer uses bundler-cache and doesn’t explicitly install/pin a Bundler version. Depending on the runner’s default Bundler, bundle install can fail with a Bundler version mismatch. Consider explicitly installing/pinning the Bundler version (or configuring ruby/setup-ruby to use the lockfile’s Bundler) before running bundle install.

Copilot uses AI. Check for mistakes.
bundler-cache: true
# bundler-cache: true

- name: unset deployment
Copy link

Copilot AI Feb 16, 2026

Choose a reason for hiding this comment

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

Step names in this workflow are capitalized (e.g., "Set up Ruby…", "Install dependencies", "Run tests"), but this new step is not. Rename it to match the existing naming style for consistency and readability.

Suggested change
- name: unset deployment
- name: Unset deployment

Copilot uses AI. Check for mistakes.
Comment on lines 19 to 23
- name: unset deployment
run: bundle config unset deployment

- name: Install dependencies
run: bundle install
Copy link

Copilot AI Feb 16, 2026

Choose a reason for hiding this comment

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

Gemfile.lock pins Bundler via BUNDLED WITH 2.2.29, but this workflow no longer uses bundler-cache and doesn’t explicitly install/pin a Bundler version. Depending on the runner’s default Bundler, bundle install can fail with a Bundler version mismatch. Consider explicitly installing/pinning the Bundler version (or configuring ruby/setup-ruby to use the lockfile’s Bundler) before running bundle install.

Copilot uses AI. Check for mistakes.
@MSD118 MSD118 closed this Feb 16, 2026
@MSD118 MSD118 deleted the masood/fix-ci-check-failing-at-set-ruby branch February 16, 2026 08:21
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.

1 participant