Skip to content

Remove '|| true' from 'docker compose up' in ci #3218

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

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

Aaron1011
Copy link
Member

@Aaron1011 Aaron1011 commented Aug 20, 2025

The 'fixtures' service no longer exits, so we don't have to ignore an unsuccessful exit code


Important

Remove '|| true' from 'docker compose' in .github/workflows/merge-queue.yml as 'fixtures' service no longer exits.

  • CI Workflow:
    • Remove '|| true' from 'docker compose' command in .github/workflows/merge-queue.yml.
    • The 'fixtures' service no longer exits, making the ignore of unsuccessful exit codes unnecessary.

This description was created by Ellipsis for ebc1d04. You can customize this summary. It will automatically update as commits are pushed.

The 'fixtures' service no longer exits, so we don't have to ignore
an unsuccessful exit code
@Copilot Copilot AI review requested due to automatic review settings August 20, 2025 20:39
Copy link
Contributor

@Copilot 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

This PR removes the || true fallback from the Docker Compose command in the CI merge queue workflow, allowing the command to fail naturally if containers exit unsuccessfully. The change reflects that the 'fixtures' service no longer exits, eliminating the need to ignore unsuccessful exit codes.

  • Removes the || true fallback from the Docker Compose up command
  • Removes the explanatory comment about handling container exit codes

Tip: Customize your code reviews with copilot-instructions.md. Create the file or learn how to get started.

@virajmehta virajmehta added this pull request to the merge queue Aug 21, 2025
@github-merge-queue github-merge-queue bot removed this pull request from the merge queue due to failed status checks Aug 21, 2025
@GabrielBianconi GabrielBianconi added this pull request to the merge queue Aug 21, 2025
@github-merge-queue github-merge-queue bot removed this pull request from the merge queue due to failed status checks Aug 21, 2025
@virajmehta virajmehta added this pull request to the merge queue Aug 21, 2025
@github-merge-queue github-merge-queue bot removed this pull request from the merge queue due to failed status checks Aug 21, 2025
@GabrielBianconi GabrielBianconi added this pull request to the merge queue Aug 22, 2025
@github-merge-queue github-merge-queue bot removed this pull request from the merge queue due to failed status checks Aug 22, 2025
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.

2 participants