Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Support for HTTP connections on GitLab merge request context provider #4259

Open
3 tasks
Patrick-Erichsen opened this issue Feb 20, 2025 · 0 comments
Open
3 tasks
Assignees
Labels
area:context-providers Relates to context providers kind:enhancement Indicates a new feature request, imrovement, or extension "needs-triage" priority:medium Indicates medium priority

Comments

@Patrick-Erichsen
Copy link
Collaborator

Before submitting your bug report

Relevant environment info

Description

I have followed the instructions here: https://docs.continue.dev/customize/context-providers#gitlab-merge-request for adding GitLab Merge Requests as a Context Provider and have successfully verified my personal access token.

Diving deeper into the code [continue/core/context/providers/GitLabMergeRequestContextProvider.ts], the getApi() function restricts the custom gitlab domain to be of a secure (https) connection but not unsecure http connection.

To reproduce

No response

Log output

@dosubot dosubot bot added area:context-providers Relates to context providers kind:enhancement Indicates a new feature request, imrovement, or extension priority:medium Indicates medium priority labels Feb 20, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area:context-providers Relates to context providers kind:enhancement Indicates a new feature request, imrovement, or extension "needs-triage" priority:medium Indicates medium priority
Projects
None yet
Development

No branches or pull requests

1 participant