Skip to content

docs: Add cursor rules file and update contributing documentation#420

Closed
devin-ai-integration[bot] wants to merge 3 commits intomainfrom
devin/1741881940-cursor-rules
Closed

docs: Add cursor rules file and update contributing documentation#420
devin-ai-integration[bot] wants to merge 3 commits intomainfrom
devin/1741881940-cursor-rules

Conversation

@devin-ai-integration
Copy link
Copy Markdown
Contributor

Add cursor rules file and update contributing documentation

This PR adds a .cursorrules file to the repository root and updates the contributing documentation to reference it. The cursor rules file includes comprehensive development guidelines covering:

  • Development setup with Poetry
  • Testing practices
  • Linting and formatting with Ruff
  • Code organization principles
  • Import conventions to avoid circular dependencies
  • Docstring standards following Google-style format

These guidelines will help developers follow the project's best practices and avoid common issues when working with the codebase.

Link to Devin run: https://app.devin.ai/sessions/f6708bbaad9642e48a33697ca19aecb3
Requested by: Aaron

Co-Authored-By: Aaron <AJ> Steers <aj@airbyte.io>
@devin-ai-integration
Copy link
Copy Markdown
Contributor Author

🤖 Devin AI Engineer

Original prompt from Aaron:

Received message in Slack channel #ask-devin-ai:

Hey, @Devin. Check in any of our existing repos have a cursor rules file. Then let's go ahead and create one for the CDK in a new PR. Check online for documentation on how to create a good cursor rules file. Use your knowledge about the CDK dev process and existing contributing docs in the repo to guide you. Ignore stale docs though, and don't update any other markdown files, with this one exception: the contributing.md file should add a reference and link to the cursorrules file.

I'll be helping with this pull request! Here's what you should know:

✅ I will automatically:

  • Address comments on this PR. Add "(aside)" to your comment to have me ignore it.
  • Look at CI failures and help fix them

Note: I can only respond to comments from users who have write access to this repository.

⚙️ Control Options:

  • Disable automatic comment and CI monitoring

@github-actions github-actions bot added the docs label Mar 13, 2025
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

Please accept my suggested wording. Also, I realized the cursor rules file should likewise cross-reference the contributing.md file, since everything in the contributing docs for humans should probably also apply to the robots.

…ules

Co-Authored-By: Aaron <AJ> Steers <aj@airbyte.io>
.cursorrules Outdated
Comment on lines +40 to +51
* Special handling for `__init__.py` files:
- Do not auto-sort imports in `__init__.py` files with isort
- When a module depends on classes defined within the same module, use the isort split directive:
```python
# Import the base class first
from .transformation import RecordTransformation

# isort: split
# Then import the implementations
from .add_fields import AddFields
from .remove_fields import RemoveFields
```
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

I believe this guidance is stale and should be fully removed.

Co-Authored-By: Aaron <AJ> Steers <aj@airbyte.io>
@devin-ai-integration
Copy link
Copy Markdown
Contributor Author

Closing due to inactivity for more than 7 days.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant