chore: update .gitignore file to adjust directory exclusions

[ssdeanx]

• Changed exclusion of 'mastra/' from wildcard to specific path

Summary by Sourcery

Chores:

• Retain current .gitignore contents with no net modifications to directory exclusions.

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
agent-stack	Error		Apr 21, 2026 11:31am

[Copilot]

Copilot wasn't able to review any files in this pull request.

[greptile-apps]

Your free trial has ended. If you'd like to continue receiving code reviews, you can add a payment method here.

[sourcery-ai]

Reviewer's guide (collapsed on small PRs)

Reviewer's Guide

.gitignore was updated to change the way the mastra directory is excluded, switching from a broad wildcard-style ignore to a more specific path-based exclusion.

File-Level Changes

Change	Details	Files
Refine .gitignore ignore rule for the mastra directory to a specific path-based exclusion.	Replace a broad/wildcard ignore rule that matched mastra-related paths with a more explicit rule targeting the mastra/ directory at a specific location Preserve existing ignore behavior for other paths while tightening the scope of the mastra directory exclusion to reduce unintended matches	.gitignore

---

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

• Contact our support team for questions or feedback.
• Visit our documentation for detailed guides and information.
• Keep in touch with the Sourcery team by following us on X/Twitter, LinkedIn or GitHub.

[coderabbitai]

Warning

Rate limit exceeded

@ssdeanx has exceeded the limit for the number of commits that can be reviewed per hour. Please wait 27 minutes and 18 seconds before requesting another review.

Your organization is not enrolled in usage-based pricing. Contact your admin to enable usage-based pricing to continue reviews beyond the rate limit, or try again in 27 minutes and 18 seconds.

⌛ How to resolve this issue?

After the wait time has elapsed, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

We recommend that you space out your commits to avoid hitting the rate limit.

🚦 How do rate limits work?

CodeRabbit enforces hourly rate limits for each developer per organization.

Our paid plans have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout.

Please see our FAQ for further information.

ℹ️ Review info

⚙️ Run configuration

Configuration used: Organization UI

Review profile: ASSERTIVE

Plan: Pro

Run ID: e3edabfd-d4dd-460c-9fda-bb7213004cc4

📥 Commits

Reviewing files that changed from the base of the PR and between d0b03d4 and 3617c5b.

📒 Files selected for processing (1)

• .gitignore

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch develop

---

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

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[github-actions]

🤖 Hi @ssdeanx, I've received your request, and I'm working on it now! You can track my progress in the logs for more details.

[sourcery-ai]

Hey - I've reviewed your changes and they look great!

---

Sourcery is free for open source - if you like our reviews please consider sharing them ✨

• X
• Mastodon
• LinkedIn
• Facebook

_{Help me be more useful! Please click 👍 or 👎 on each comment and I'll use the feedback to improve your reviews.}

[github-actions]

🤖 I'm sorry @ssdeanx, but I was unable to process your request. Please see the logs for more details.

[gemini-code-assist]

Code Review

This pull request updates the .gitignore file by modifying the exclusion pattern for the mastra/ directory. The review feedback suggests anchoring the pattern with a leading slash to ensure it only targets the root directory and avoids redundant or unintended exclusions of nested directories.

[gemini-code-assist]

The pattern mastra/ matches any directory named mastra at any depth in the project (e.g., src/mastra/). If the goal is to target a 'specific path' at the root (as mentioned in the PR description) and avoid accidentally ignoring directories like src/mastra/, it should be anchored with a leading slash. Note that there are already several specific exclusions for files under src/mastra/ later in this file (e.g., lines 204, 207, 229), which would be rendered redundant if the entire mastra/ directory is ignored globally.

/mastra/