Small improvement

[Weves]

Description

^

How Has This Been Tested?

[Describe the tests you ran to verify your changes]

Backporting (check the box to trigger backport action)

Note: You have to check that the action passes, otherwise resolve the conflicts manually and tag the patches.

• This PR should be backported (make sure to check that the backport attempt succeeds)
• [Optional] Override Linear Check

---

Summary by cubic

Use .is_(False) to filter out user files in get_connector_credential_pairs_for_user. This follows SQLAlchemy best practices and removes the linter suppression.

[vercel]

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

Project	Deployment	Preview	Comments	Updated (UTC)
internal-search	Ready	Preview	Comment	Aug 25, 2025 0:53am

[greptile-apps]

Greptile Summary

This PR makes a small but meaningful improvement to SQL query consistency in the connector_credential_pair.py file. The change replaces a direct boolean comparison (!= True) with SQLAlchemy's .is_(False) method on line 148 when filtering out user files in the query.

The modification standardizes the codebase's approach to boolean comparisons in SQLAlchemy queries. While functionally equivalent, the .is_(False) method is more explicit about NULL handling - records where is_user_file is NULL will be included in the results, which is the intended behavior. This aligns with SQLAlchemy best practices and creates consistency with other parts of the codebase that already use the .is_() method (as seen on lines 657 and 659 in the same file).

The change affects the get_connector_credential_pairs_for_user function, which is a core database query function used throughout the application to retrieve connector-credential pairs while filtering out user files when include_user_files=False. This function is called by various parts of the system that need to work with connector configurations.

Confidence score: 4/5

• This PR is safe to merge with minimal risk as it's a syntactic improvement that maintains identical functionality
• Score reflects that this is a straightforward refactoring to improve code consistency and follows SQLAlchemy best practices
• No files require special attention as the change is isolated and well-understood

_{1 file reviewed, no comments}

_{Edit Code Review Bot Settings | Greptile}

[cubic-dev-ai]

No issues found across 1 file

[Subash-Mohan]

lgtm