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

Integration requests form #440

Merged
merged 2 commits into from
May 20, 2024
Merged

Integration requests form #440

merged 2 commits into from
May 20, 2024

Conversation

rflihxyz
Copy link
Contributor

No description provided.

Copy link

vercel bot commented May 20, 2024

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name Status Preview Comments Updated (UTC)
panora-client-ts 🔄 Building (Inspect) Visit Preview 💬 Add feedback May 20, 2024 5:24am

Copy link

changeset-bot bot commented May 20, 2024

⚠️ No Changeset found

Latest commit: be3c748

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

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

Copy link
Contributor

coderabbitai bot commented May 20, 2024

Walkthrough

The recent updates to the .github/ISSUE_TEMPLATE/new-integration-request.yml file involve refining the structure and clarity of the form. A new title field has been added, the id: vertical field has been renamed to id: software_category, and the options under software_category have been updated to better reflect the categories of software. These changes aim to enhance the user experience and improve categorization.

Changes

Files Change Summary
.github/ISSUE_TEMPLATE/new-integration-request.yml Added title field, renamed id: vertical to id: software_category, updated options under software_category, and adjusted corresponding labels and descriptions.

In the land of code where rabbits play,
A template change has come our way.
With titles clear and categories bright,
We hop through forms with pure delight.
🐇✨ In software fields, we organize,
Each change a gem in coder's eyes.
🌟📂


Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

Share
Tips

Chat

There are 3 ways to chat with CodeRabbit:

  • Review comments: Directly reply to a review comment made by CodeRabbit. Example:
    • I pushed a fix in commit <commit_id>.
    • Generate unit testing code for this file.
    • Open a follow-up GitHub issue for this discussion.
  • 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 generate unit testing code for this file.
    • @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 generate interesting stats about this repository and render them as a table.
    • @coderabbitai show all the console.log statements in this repository.
    • @coderabbitai read src/utils.ts and generate unit testing code.
    • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.

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 as PR comments)

  • @coderabbitai pause to pause the reviews on a PR.
  • @coderabbitai resume to resume the paused reviews.
  • @coderabbitai review to trigger a review. This is useful when automatic reviews are disabled for the repository.
  • @coderabbitai resolve resolve all the CodeRabbit review comments.
  • @coderabbitai help to get help.

Additionally, you can add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.

CodeRabbit Configration 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.

@rflihxyz rflihxyz merged commit 1da8e88 into main May 20, 2024
13 of 16 checks passed
Copy link
Contributor

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

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

Actionable comments posted: 1

Review Details

Configuration used: CodeRabbit UI
Review profile: CHILL

Commits Files that changed from the base of the PR and between 66dc7de and be3c748.
Files selected for processing (1)
  • .github/ISSUE_TEMPLATE/new-integration-request.yml (2 hunks)
Additional comments not posted (4)
.github/ISSUE_TEMPLATE/new-integration-request.yml (4)

3-3: The title format is clear and specific, which is good for automatic issue labeling and sorting.


21-21: The updated label "Category" aligns well with the new ID, enhancing clarity.


22-22: Allowing multiple selections in the category dropdown enhances flexibility for the users.


26-41: The updated options in the dropdown cover a broad range of software categories, which should enhance the form's utility.

@@ -15,16 +16,29 @@ body:
validations:
required: true
- type: dropdown
id: vertical
id: software_category
Copy link
Contributor

Choose a reason for hiding this comment

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

Tip

Codebase Verification

Ensure that any scripts or automation that previously used id: vertical are updated to accommodate the new id: software_category. The search results indicate multiple occurrences of the term "vertical" across various files, including scripts, services, and documentation. These references need to be reviewed and updated accordingly.

  • packages/api/swagger/swagger-spec.json
  • packages/shared/src/providers.ts
  • packages/shared/src/utils.ts
  • packages/shared/src/envConfig.ts
  • packages/shared/src/authUrl.ts
  • packages/api/src/ticketing/user/sync/sync.service.ts
  • packages/api/scripts/oauthConnector.js
  • packages/api/scripts/commonObject.sh
  • packages/api/scripts/connectorUpdate.js
  • packages/api/src/crm/task/sync/sync.service.ts
  • packages/api/src/@core/field-mapping/field-mapping.service.ts
  • packages/api/src/@core/sync/sync.service.ts
  • packages/api/src/@core/passthrough/passthrough.service.ts
  • packages/api/src/@core/connections-strategies/connections-strategies.service.ts
  • docs/quick-start.mdx
  • docs/open-source/contributors.mdx
  • docs/glossary/connection-object.mdx
  • docs/core-concepts/embedded-catalog.mdx
  • docs/core-concepts/auth.mdx
  • INTEGRATIONS.md
  • apps/embedded-catalog/react/src/index.tsx
  • apps/client-ts/src/state/verticalStore.ts
  • apps/client-ts/src/hooks/useProviderProperties.tsx
  • apps/client-ts/src/components/Connection/ConnectionTable.tsx
  • apps/client-ts/src/components/Configuration/Connector/VerticalSelector.tsx
  • apps/client-ts/src/components/Configuration/Connector/ConnectorList.tsx
  • apps/client-ts/src/components/Configuration/Connector/ConnectorDisplay.tsx
  • apps/client-ts/src/components/Configuration/AddAuthCredentialsForm.tsx
  • apps/magic-link/src/hooks/useOAuth.ts
Analysis chain

Ensure that any scripts or automation that previously used id: vertical are updated to accommodate the new id: software_category.

Scripts Executed

The following scripts were executed for the analysis:


Script:

#!/bin/bash
# Description: Search for occurrences of the old ID 'vertical' to ensure they are updated.

# Test: Search for the old ID usage. Expect: No occurrences of 'vertical'.
rg --type yaml $'id: vertical'

Length of output: 31



Script:

#!/bin/bash
# Description: Search for occurrences of the old ID 'vertical' in all file types to ensure they are updated.

# Test: Search for the old ID usage in all files. Expect: No occurrences of 'vertical'.
rg 'id: vertical'

Length of output: 19



Script:

#!/bin/bash
# Description: Search for occurrences of the old ID 'vertical' in scripts and documentation to ensure they are updated.

# Test: Search for the old ID usage in scripts and documentation. Expect: No occurrences of 'vertical'.
rg 'vertical'

Length of output: 50239

@rflihxyz rflihxyz deleted the integration-requests-form branch June 11, 2024 16:04
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

1 participant