Skip to content

Delete .circleci directory - #91

Merged
Dargon789 merged 1 commit into
mainfrom
Dargon789-patch-3
Feb 2, 2026
Merged

Dargon789 merged 1 commit into
mainfrom
Dargon789-patch-3

Conversation

@Dargon789

@Dargon789 Dargon789 commented Feb 2, 2026 •

Copy link
Copy Markdown
Owner

What changed? Why?

Notes to reviewers

How has it been tested?

Summary by Sourcery

CI:

  • Delete obsolete CircleCI configuration and pipeline definition files.

@vercel

vercel Bot commented Feb 2, 2026

Copy link
Copy Markdown

Deployment failed with the following error:

Resource is limited - try again in 9 hours (more than 100, code: "api-deployments-free-per-day").

Learn More: https://vercel.com/dargon789-forge?upgradeToPro=build-rate-limit

@snyk-io

snyk-io Bot commented Feb 2, 2026 •

Copy link
Copy Markdown

✅ Snyk checks have passed. No issues have been found so far.

Status Scanner Critical High Medium Low Total (0)
✅ Open Source Security 0 0 0 0 0 issues

💻 Catch issues earlier using the plugins for VS Code, JetBrains IDEs, Visual Studio, and Eclipse.

@gemini-code-assist

Copy link
Copy Markdown

Summary of Changes

Hello @Dargon789, I'm Gemini Code Assist1! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request streamlines the project's CI/CD setup by completely removing the existing CircleCI configuration. This action indicates a shift away from CircleCI for automated builds and deployments, potentially in favor of another CI/CD solution or a temporary pause in automated workflows.

Highlights

  • CircleCI Configuration Removal: The entire .circleci directory, containing ci-foundry.yml and config.yml, has been deleted. This action removes all CircleCI continuous integration/continuous deployment configurations from the repository.
Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature Command Description
Code Review /gemini review Performs a code review for the current pull request in its current state.
Pull Request Summary /gemini summary Provides a summary of the current pull request in its current state.
Comment @gemini-code-assist Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help /gemini help Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

Footnotes

  1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution. ↩

@github-actions

github-actions Bot commented Feb 2, 2026 •

Copy link
Copy Markdown

Dependency Review

✅ No vulnerabilities or license issues or OpenSSF Scorecard issues found.

Scanned Files

None

@gemini-code-assist gemini-code-assist Bot 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.

Code Review

This pull request removes the CircleCI configuration by deleting the .circleci directory. While the change itself is simple, the pull request description lacks an explanation for this removal. It's important to document why the CI/CD pipeline is being removed, for instance, if it's being replaced by another system or if it's no longer needed. This context is vital for maintaining a clear history of the project's development practices.

I am having trouble creating individual review comments. Click here to see my feedback.

.circleci/config.yml (1-31)

high

Removing the CircleCI configuration disables the project's continuous integration pipeline. This is a significant change to the development workflow. If a new CI/CD system is replacing CircleCI, its configuration should be added as part of this PR to avoid a gap in automated testing and builds. If CI/CD is being removed entirely, this should be documented in the PR description to clarify the rationale for future maintainers.

@sourcery-ai

sourcery-ai Bot commented Feb 2, 2026 •

Copy link
Copy Markdown
Reviewer's guide (collapsed on small PRs)

Reviewer's Guide

.circleci CI configuration has been fully removed from the repository by deleting the entire .circleci directory.

File-Level Changes

Change Details Files
Remove legacy CircleCI pipeline configuration from version control.
  • Delete CircleCI job/pipeline definitions stored in ci-foundry configuration
  • Delete primary CircleCI config that defined workflows and project-level settings
.circleci/ci-foundry.yml
.circleci/config.yml

Tips and commands

Interacting with Sourcery

  • Trigger a new review: Comment @sourcery-ai review on the pull request.
  • Continue discussions: Reply directly to Sourcery's review comments.
  • Generate a GitHub issue from a review comment: Ask Sourcery to create an
    issue from a review comment by replying to it. You can also reply to a
    review comment with @sourcery-ai issue to create an issue from it.
  • Generate a pull request title: Write @sourcery-ai anywhere in the pull
    request title to generate a title at any time. You can also comment
    @sourcery-ai title on the pull request to (re-)generate the title at any time.
  • Generate a pull request summary: Write @sourcery-ai summary anywhere in
    the pull request body to generate a PR summary at any time exactly where you
    want it. You can also comment @sourcery-ai summary on the pull request to
    (re-)generate the summary at any time.
  • Generate reviewer's guide: Comment @sourcery-ai guide on the pull
    request to (re-)generate the reviewer's guide at any time.
  • Resolve all Sourcery comments: Comment @sourcery-ai resolve on the
    pull request to resolve all Sourcery comments. Useful if you've already
    addressed all the comments and don't want to see them anymore.
  • Dismiss all Sourcery reviews: Comment @sourcery-ai dismiss on the pull
    request to dismiss all existing Sourcery reviews. Especially useful if you
    want to start fresh with a new review - don't forget to comment
    @sourcery-ai review to trigger a new review!

Customizing Your Experience

Access your dashboard to:

  • Enable or disable review features such as the Sourcery-generated pull request
    summary, the reviewer's guide, and others.
  • Change the review language.
  • Add, remove or edit custom review instructions.
  • Adjust other review settings.

Getting Help

@sourcery-ai sourcery-ai Bot 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.

Hey - I've left some high level feedback:

  • Since the .circleci directory is being removed entirely, double-check for any remaining references to CircleCI config or workflows in build scripts (e.g., Makefiles, package.json scripts, or CI-related helper scripts) and clean those up to avoid dead paths or commands.
Prompt for AI Agents
Please address the comments from this code review:

## Overall Comments
- Since the `.circleci` directory is being removed entirely, double-check for any remaining references to CircleCI config or workflows in build scripts (e.g., Makefiles, package.json scripts, or CI-related helper scripts) and clean those up to avoid dead paths or commands.

Sourcery is free for open source - if you like our reviews please consider sharing them ✨
Help me be more useful! Please click 👍 or 👎 on each comment and I'll use the feedback to improve your reviews.

Signed-off-by: Dargon789 <64915515+Dargon789@users.noreply.github.com>
@vercel

vercel Bot commented Feb 2, 2026

Copy link
Copy Markdown

Deployment failed with the following error:

Resource is limited - try again in 8 hours (more than 100, code: "api-deployments-free-per-day").

Learn More: https://vercel.com/dargon789-forge?upgradeToPro=build-rate-limit

@Dargon789
Dargon789 merged commit dca4eef into main Feb 2, 2026
11 of 20 checks passed
@Dargon789
Dargon789 deleted the Dargon789-patch-3 branch February 2, 2026 04:38
@Dargon789 Dargon789 linked an issue Mar 17, 2026 that may be closed by this pull request
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

1 participant