Skip to content

refactor!: Repo structure#5405

Open
ark0f wants to merge 19 commits intomasterfrom
al/repo-structure
Open

refactor!: Repo structure#5405
ark0f wants to merge 19 commits intomasterfrom
al/repo-structure

Conversation

@ark0f
Copy link
Copy Markdown
Member

@ark0f ark0f commented May 4, 2026

Related to #5374

@semanticdiff-com
Copy link
Copy Markdown

semanticdiff-com Bot commented May 4, 2026

Review changes with  SemanticDiff

@gemini-code-assist
Copy link
Copy Markdown
Contributor

Summary of Changes

Hello, 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 performs a comprehensive refactor of the repository's directory structure. The goal is to improve maintainability and clarity by grouping related modules into dedicated folders. This change affects the entire project, requiring updates to internal dependency paths and build configurations to align with the new layout.

Highlights

  • Repository Restructuring: The repository has undergone a significant reorganization, moving core components, programs, and infrastructure into more logical directories such as 'vara/', 'core/', 'program/', and '.github/'.
  • Dependency Updates: The 'Cargo.toml' file has been updated to reflect the new directory structure, ensuring all internal dependencies and examples point to their new locations.
  • Cleanup: Removed the 'codecov.yml' configuration file and 'galloc/README.md' as part of the repository cleanup.
Ignored Files
  • Ignored by pattern: .github/workflows/** (7)
    • .github/workflows/Build-gear-loader-network.yml
    • .github/workflows/CI-docker-gear.yml
    • .github/workflows/benchmarks.yml
    • .github/workflows/build-node-fuzzer.yaml
    • .github/workflows/check-node-sync.yml
    • .github/workflows/test-measurements.yaml
    • .github/workflows/validation.yml
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.

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.

Copy link
Copy Markdown
Contributor

@gemini-code-assist gemini-code-assist Bot left a comment

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 performs a significant restructuring of the repository, moving crates into categorized subdirectories such as vara/, core/, program/, and utils/, and updating workspace configurations and dependency paths accordingly. Feedback indicates that several moved crates were omitted from the members list in the root Cargo.toml, which would break workspace-wide operations like builds and tests. Additionally, a redundant entry was identified in the workspace members list.

Comment thread Cargo.toml Outdated
Copy link
Copy Markdown

@chatgpt-codex-connector chatgpt-codex-connector Bot left a comment

Choose a reason for hiding this comment

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

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 1a4709deeb

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

Comment thread vara/sdk/gcli/tests/util.rs Outdated
@breathx breathx added type: refactor Internal improvements without changing behavior ci: full Run full CI matrix (all platforms and profiles) and removed A0-pleasereview labels May 5, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

ci: full Run full CI matrix (all platforms and profiles) type: refactor Internal improvements without changing behavior

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants