chore: update .gitignore to not commit junit results

[Aaron ("AJ") Steers (aaronsteers)]

Summary by CodeRabbit

• Chores
  • Updated repository settings to ignore build and test result directories, preventing these files from being tracked in version control.

Important

Auto-merge enabled.

This PR is set to merge automatically when all requirements are met.

[Copilot]

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

[coderabbitai]

📝 Walkthrough

Walkthrough

The .gitignore file was updated to add new rules for ignoring the build and test-results directories, ensuring that build artifacts and test outputs are not tracked by Git. No other files or existing rules were modified.

Changes

File(s)	Change Summary
.gitignore	Added rules to ignore build and test-results directories under a new comment section.

---

Would you like to consider adding patterns for other common build or test artifact directories, such as dist or .coverage, to further streamline your repository? Wdyt?

---

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:

‼️ IMPORTANT
Auto-reply has been disabled for this repository in the CodeRabbit settings. The CodeRabbit bot will not respond to your replies unless it is explicitly tagged.

• 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.

[coderabbitai]

Actionable comments posted: 0

🧹 Nitpick comments (1)

.gitignore (1)

1-3: New ignore rules for build and test-results directories
These entries will skip all build and test-results paths, which is great to keep artifacts out of Git. Would you consider adding trailing slashes (e.g. build/ and test-results/) to explicitly mark them as directories and avoid unintentionally ignoring files named “build”? wdyt?

📜 Review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between acc1003 and 78934e8.

📒 Files selected for processing (1)

• .gitignore (1 hunks)

⏰ Context from checks skipped due to timeout of 90000ms (6)

• GitHub Check: MyPy Check
• GitHub Check: Pytest (Fast)
• GitHub Check: SDM Docker Image Build
• GitHub Check: preview_docs
• GitHub Check: Analyze (python)
• GitHub Check: Analyze (actions)

[github-actions]

PyTest Results (Fast)

3 657 tests  ±0   3 647 ✅ ±0   5m 43s ⏱️ -4s
    1 suites ±0      10 💤 ±0 
    1 files   ±0       0 ❌ ±0 

Results for commit 78934e8. ± Comparison against base commit acc1003.

♻️ This comment has been updated with latest results.

[Aaron ("AJ") Steers (aaronsteers)]

Something flaky appears to be happening here:

https://github.com/airbytehq/airbyte-python-cdk/actions/runs/15497060794/job/43636202348

This only failed in the fast tests, not in the full tests, and the PR doesn't change any code.