You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
resolve: Enhance security for GitHub repository access
Why is this change needed?
This refactoring improves security by moving GitHub repository API calls from client-side to server-side. Previously, Supabase client credentials were exposed to the browser, making it easier for attackers to access sensitive data. With this change, all repository data is now fetched through a dedicated API route with proper authentication checks.
What would you like reviewers to focus on?
Verify API route security implementation (authentication, error handling)
Check if the UX remains consistent with the previous implementation
Review the form-based approach for importing repositories
Testing Verification
Tested repository fetching with valid and invalid installation IDs
Verified authentication is properly enforced
Confirmed error states are handled and displayed correctly
Tested project import flow with various repositories
What was done
pr_agent:summary
Detailed Changes
pr_agent:walkthrough
Additional Notes
This change is part of ongoing security improvements to reduce client-side credential exposure.
Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.
This PR includes no changesets
When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types
Tasks are run on every commit but only new migration files are pushed.
Close and reopen this PR if you want to apply changes from existing seed or migration files.
…lation ID and refactor ProjectNewPage components
- Added a new API route to fetch GitHub repositories based on the installation ID.
- Updated ProjectNewPage to require organizationId as a mandatory prop.
- Refactored InstallationSelector to utilize a new RepositoriesPanel component for displaying repositories.
- Removed redundant repository fetching logic from InstallationSelector and centralized it in RepositoriesPanel.
- Updated RepositoryItem to handle form submissions for adding projects.
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
MH4GF
force-pushed
the
refactor-installation-selector
branch
from
Issue
Why is this change needed?
This refactoring improves security by moving GitHub repository API calls from client-side to server-side. Previously, Supabase client credentials were exposed to the browser, making it easier for attackers to access sensitive data. With this change, all repository data is now fetched through a dedicated API route with proper authentication checks.
What would you like reviewers to focus on?
Testing Verification
What was done
pr_agent:summary
Detailed Changes
pr_agent:walkthrough
Additional Notes
This change is part of ongoing security improvements to reduce client-side credential exposure.