👷 Build and test during CI

[NatoBoram]

• Closes Some tests are failing #44
• Closes 👷 Build and test during CI coderabbitai/langs#24

Summary by CodeRabbit

• Chores
  • Streamlined the dependency installation process to ensure all setup scripts execute properly.
  • Introduced a unified build and test step to enhance overall project quality.
  • Updated repository settings to exclude outdated local dependency caches.
  • Adjusted package dependencies for improved stability and compatibility.

[coderabbitai]

Walkthrough

The pull request updates the CI workflow, modifies the repository’s ignore rules, and adjusts a dependency in the TOML package. The CI workflow now installs dependencies without skipping scripts and introduces a new "Build and test" step that compiles TypeScript, sources files, builds the project, and runs tests. The .gitignore file now excludes the .pnpm-store directory. Additionally, the dependency for @ast-grep/setup-lang is changed from a workspace reference to a fixed version (0.0.3).

Changes

File(s)	Change Summary
.github/workflows/ci.yml	Dependency installation updated from pnpm install --ignore-scripts to pnpm install. Added a new "Build and test" step with commands: compile-ts, source, build, and test.
.gitignore	Added a new entry .pnpm-store to ignore the pnpm store directory.
packages/toml/package.json	Updated dependency for @ast-grep/setup-lang from "workspace:*" to "0.0.3".

Sequence Diagram(s)

sequenceDiagram
    participant CI as "CI Workflow"
    participant IN as "pnpm Install"
    participant BT as "Build & Test"
    participant CT as "Compile TypeScript"
    participant SRC as "Source Files"
    participant BLD as "Build Project"
    participant TST as "Run Tests"

    CI->>IN: Execute pnpm install
    CI->>BT: Initiate "Build and test" step
    BT->>CT: Run pnpm -r compile-ts
    CT-->>BT: Return compilation result
    BT->>SRC: Run pnpm -r source
    SRC-->>BT: Return sourcing result
    BT->>BLD: Run pnpm -r build
    BLD-->>BT: Return build result
    BT->>TST: Run pnpm -r test
    TST-->>BT: Return test results

Loading

Poem

I’m a coding bunny, quick on my feet,
Hopping through CI, where commands meet.
I see dependencies set to run without a hitch,
And tests that compile, build, and switch.
With a final nibble of .pnpm-store in the burrow,
I celebrate these changes—a joyful workflow!
🥕✨

---

📜 Recent review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between 4361a20 and 97d05c5.

⛔ Files ignored due to path filters (1)

• pnpm-lock.yaml is excluded by !**/pnpm-lock.yaml

📒 Files selected for processing (3)

• .github/workflows/ci.yml (1 hunks)
• .gitignore (1 hunks)
• packages/toml/package.json (1 hunks)

🔇 Additional comments (4)

.gitignore (1)

1-2: Added PNPM Store Ignore Rule.
The new lines correctly introduce an ignore directive for .pnpm-store, which is created during pnpm installations. This update keeps the repository clean by preventing tracking of build artifacts and caches.

packages/toml/package.json (1)

24-26: Updated Dependency for @ast-grep/setup-lang.
Changing the dependency from a workspace reference to a fixed version ("0.0.3") improves reproducibility in CI environments and ensures that the expected version is installed. Make sure this version remains compatible with the rest of your ecosystem.

.github/workflows/ci.yml (2)

25-26: Revised Dependency Installation Command.
Switching from pnpm install --ignore-scripts to pnpm install ensures that all necessary post-install scripts are executed during CI. This is important for triggering build steps like generating parsers or other setup tasks.

---

27-33: Introduced a Build and Test Step.
The new "Build and test" step, which recursively runs commands to compile TypeScript, source files, build the project, and run tests, aligns well with the CI objectives. This step helps ensure that changes are validated through a complete build process.

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

🪧 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.
  • Generate unit testing code for this file.
  • 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 generate unit testing code for this file.
  • @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 generate unit testing code.
  • @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.

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 resolve resolve all the CodeRabbit review comments.
• @coderabbitai plan to trigger planning for file edits and PR creation.
• @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.

[HerringtonDarkholme]

thanks!