Skip to content

Move from rook directory to root directory#189

Merged
reddevilmidzy merged 2 commits intomainfrom
move-directory
Jul 22, 2025
Merged

Move from rook directory to root directory#189
reddevilmidzy merged 2 commits intomainfrom
move-directory

Conversation

@reddevilmidzy
Copy link
Owner

@reddevilmidzy reddevilmidzy commented Jul 22, 2025

♟️ What’s this PR about?

Move from rook directory to root directory, and cargo update

Summary by CodeRabbit

  • Chores
    • Updated configuration files and workflows to operate from the repository root instead of a subdirectory.
    • Expanded and reorganized the .gitignore to cover more general patterns and IDE/editor files.
    • Adjusted the path to the README file in the project manifest for improved consistency.
    • Removed obsolete or redundant placeholder and ignore files.

Copilot AI review requested due to automatic review settings July 22, 2025 07:49
@coderabbitai
Copy link
Contributor

coderabbitai bot commented Jul 22, 2025

Walkthrough

The changes shift configuration, workflow, and ignore patterns from the rook subdirectory to the repository root. This includes updating workflow paths, dependabot scope, ignore files, and manifest references to apply globally. Redundant or now-unnecessary files in subdirectories are deleted, and ignore patterns are broadened and reorganized for clarity.

Changes

File(s) Change Summary
.github/dependabot.yml Changed cargo directory scope from /rook/ to / (root) for dependency updates.
.github/workflows/rust.yml,
.github/workflows/shuttle_deploy.yml
Updated workflow steps and cache paths to operate from root instead of rook subdirectory.
.gitignore Generalized and expanded ignore patterns; removed rook/ prefixes; added IDE/editor files.
rook/.gitignore,
pawn/.gitkeep
Deleted subdirectory-specific ignore and placeholder files.
Cargo.toml Changed readme path from ../README.md to README.md.

Estimated code review effort

1 (~6 minutes)

Poem

In the garden of code, a rabbit hops,
Cleaning old paths, making tidy stops.
From rook to root, the files align,
Ignore lists bloom, configurations refine.
Subfolders now lighter, the root takes the lead—
A burrow made simple, for all code to succeed! 🐇✨


🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

  • Review comments: Directly reply to a review comment made by CodeRabbit. Example:
    • I pushed a fix in commit <commit_id>, please review it.
    • Explain this complex logic.
    • Open a follow-up GitHub issue for this discussion.
  • Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
    • @coderabbitai explain this code block.
    • @coderabbitai modularize this function.
  • PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
    • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
    • @coderabbitai read src/utils.ts and explain its main purpose.
    • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
    • @coderabbitai help me debug CodeRabbit configuration file.

Support

Need help? Create a ticket on our support page for assistance with any issues or questions.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

  • @coderabbitai pause to pause the reviews on a PR.
  • @coderabbitai resume to resume the paused reviews.
  • @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
  • @coderabbitai full review to do a full review from scratch and review all the files again.
  • @coderabbitai summary to regenerate the summary of the PR.
  • @coderabbitai generate docstrings to generate docstrings for this PR.
  • @coderabbitai generate sequence diagram to generate a sequence diagram of the changes in this PR.
  • @coderabbitai resolve resolve all the CodeRabbit review comments.
  • @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
  • @coderabbitai help to get help.

Other keywords and placeholders

  • Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
  • Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
  • Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

  • You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
  • Please see the configuration documentation for more information.
  • If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

  • Visit our Documentation for detailed information on how to use CodeRabbit.
  • Join our Discord Community to get help, request features, and share feedback.
  • Follow us on X/Twitter for updates and announcements.

@github-actions github-actions bot added this to the 5차 MVP 구현 milestone Jul 22, 2025
Copy link
Contributor

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 moves the Rust project structure from a nested rook/ directory to the root directory of the repository. This reorganization simplifies the project layout and eliminates the need for subdirectory-specific configurations.

Key changes:

  • Relocated Rust project files from rook/ subdirectory to repository root
  • Updated CI/CD workflows to remove working-directory specifications
  • Modified configuration paths in GitHub Actions and Dependabot to point to root directory

Reviewed Changes

Copilot reviewed 6 out of 51 changed files in this pull request and generated no comments.

Show a summary per file
File Description
rook/.gitignore Removed gitignore file from old rook directory
pawn/.gitkeep Removed placeholder file from pawn directory
Cargo.toml Updated readme path to point to root directory
.github/workflows/shuttle_deploy.yml Removed working-directory specification for shuttle deployment
.github/workflows/rust.yml Updated all cargo commands and paths to work from root directory
.github/dependabot.yml Changed cargo directory monitoring from /rook/ to root

Copy link
Contributor

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

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

Actionable comments posted: 0

🔭 Outside diff range comments (1)
Cargo.toml (1)

4-9: edition = "2024" is not yet stable – CI will break

Rust editions released so far are 2015, 2018 and 2021.
Using the unreleased 2024 edition will cause cargo to fail on stable, beta and nightly toolchains.

- edition = "2024"
+ edition = "2021"

Update the edition (and run cargo fix --edition) before merging.

🧹 Nitpick comments (2)
.gitignore (1)

1-10: Nice generalisation – consider a few extra common entries

You might also want to ignore OS-specific noise files:

+# macOS
+.DS_Store
+
+# Windows
+Thumbs.db
+Desktop.ini
.github/workflows/rust.yml (1)

55-57: Avoid cache-key & path duplication

The same cache stanza appears in four jobs. Extract into a reusable composite action or use a job-level strategy.matrix with a single step to keep the workflow DRY.

Illustrative snippet:

- name: Cache Cargo
  uses: actions/cache@v4
  with:
    path: |
      ~/.cargo/registry
      ~/.cargo/git
      target
    key: ${{ runner.os }}-cargo-${{ hashFiles('**/Cargo.lock') }}

Also applies to: 81-83, 117-119, 158-161

📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between eb98294 and 07bb1c6.

⛔ Files ignored due to path filters (1)
  • Cargo.lock is excluded by !**/*.lock
📒 Files selected for processing (7)
  • .github/dependabot.yml (1 hunks)
  • .github/workflows/rust.yml (6 hunks)
  • .github/workflows/shuttle_deploy.yml (0 hunks)
  • .gitignore (1 hunks)
  • Cargo.toml (1 hunks)
  • pawn/.gitkeep (0 hunks)
  • rook/.gitignore (0 hunks)
💤 Files with no reviewable changes (3)
  • pawn/.gitkeep
  • .github/workflows/shuttle_deploy.yml
  • rook/.gitignore
⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (1)
  • GitHub Check: build
🔇 Additional comments (4)
.github/dependabot.yml (1)

10-12: Root-level scope looks good – double-check nested crates

Changing the Cargo directory to / will work only if every publishable crate now lives at the repo root.
If you still keep additional crates/workspaces in sub-folders, Dependabot will ignore them.
Confirm the crate layout or add extra update blocks for each nested crate.

Cargo.toml (1)

8-9: README path updated – ensure file really exists at root

The manifest now points to README.md. Make sure this file was actually moved to the repository root, otherwise cargo publish and doc links will error out.

.github/workflows/rust.yml (2)

33-36: Correct manifest path 👍

Pointing cargo-deny at ./Cargo.toml matches the new layout. No issues spotted.


170-174: Coverage upload path matches build output

cargo llvm-cov writes lcov.info at the working directory, so the updated path-to-lcov is correct.

@coveralls-official
Copy link

Pull Request Test Coverage Report for Build 16438119497

Details

  • 0 of 0 changed or added relevant lines in 0 files are covered.
  • No unchanged relevant lines lost coverage.
  • Overall coverage remained the same at 74.414%

Totals Coverage Status
Change from base Build 16437241252: 0.0%
Covered Lines: 1588
Relevant Lines: 2134

💛 - Coveralls

@reddevilmidzy reddevilmidzy merged commit d41da62 into main Jul 22, 2025
7 checks passed
@reddevilmidzy reddevilmidzy deleted the move-directory branch July 22, 2025 07:58
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