-
Notifications
You must be signed in to change notification settings - Fork 10
Fixed GitHub alignment issues and notes in AI #259
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
Changes from 2 commits
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
| Original file line number | Diff line number | Diff line change | ||||
|---|---|---|---|---|---|---|
|
|
@@ -36,130 +36,137 @@ To configure GitHub integration, you'll need to create a GitHub App within your | |||||
|
|
||||||
| == GitHub Cloud {#github-cloud} | ||||||
|
|
||||||
| Follow these steps to create a GitHub App, set callback URLs, and configure webhooks so Plane can sync PRs and commits from GitHub Cloud. | ||||||
| Follow these steps to create a GitHub App, set callback URLs, and configure webhooks so Plane can sync PRs and commits from GitHub Cloud. | ||||||
|
|
||||||
| #### GitHub Cloud | ||||||
| #### GitHub Cloud | ||||||
|
|
||||||
| 1. Go to **Settings \> Developer Settings \> GitHub Apps** in your GitHub organization. | ||||||
| 1. Go to **Settings \> Developer Settings \> GitHub Apps** in your GitHub organization. | ||||||
|
|
||||||
| 2. Click **New GitHub App**. | ||||||
|  | ||||||
| 2. Click **New GitHub App**. | ||||||
|
|
||||||
| 3. In the **Register new GitHub App** page, provide a **GitHub App name** and **Homepage URL**. | ||||||
|  | ||||||
|  | ||||||
|
|
||||||
| 4. In the **Identifying and authorizing users** section, add the following **Callback URLS**. | ||||||
| 3. In the **Register new GitHub App** page, provide a **GitHub App name** and **Homepage URL**. | ||||||
|
|
||||||
| ```bash | ||||||
| https://<your-domain>/silo/api/github/auth/callback | ||||||
| https://<your-domain>/silo/api/github/auth/user/callback | ||||||
| ``` | ||||||
|  | ||||||
|
|
||||||
| These URLs allow Plane to verify and enable workspace connection with the Github App. | ||||||
|  | ||||||
| 4. In the **Identifying and authorizing users** section, add the following **Callback URLS**. | ||||||
|
|
||||||
| :::warning | ||||||
| Make sure to opt out of **Expire user authorization tokens** feature. | ||||||
| ::: | ||||||
| ```bash | ||||||
| https://<your-domain>/silo/api/github/auth/callback | ||||||
| https://<your-domain>/silo/api/github/auth/user/callback | ||||||
| ``` | ||||||
|
|
||||||
| 5. In the **Post installation** section, add the below **Setup URL**. | ||||||
| These URLs allow Plane to verify and enable workspace connection with the Github App. | ||||||
|
|
||||||
| ```bash | ||||||
| https://<your-domain>/silo/api/github/auth/callback | ||||||
| ``` | ||||||
|  | ||||||
|
|
||||||
| Redirects users to this URL after GitHub app installation. | ||||||
|  | ||||||
| :::warning | ||||||
| Make sure to opt out of **Expire user authorization tokens** feature. | ||||||
| ::: | ||||||
|
|
||||||
| 6. Turn on **Redirect on update**. | ||||||
| 5. In the **Post installation** section, add the below **Setup URL**. | ||||||
|
|
||||||
| 7. In the **Webhook** section, add the below **Webhook URL**. | ||||||
| ```bash | ||||||
| https://<your-domain>/silo/api/github/auth/callback | ||||||
| ``` | ||||||
|
|
||||||
| ```bash | ||||||
| https://<your-domain>/silo/api/github/github-webhook | ||||||
| ``` | ||||||
| Redirects users to this URL after GitHub app installation. | ||||||
|
|
||||||
|  | ||||||
|
|
||||||
| This allows Plane to receive updates from GitHub repositories. | ||||||
| 6. Turn on **Redirect on update**. | ||||||
|
|
||||||
|  | ||||||
| 7. In the **Webhook** section, add the below **Webhook URL**. | ||||||
|
|
||||||
| ```bash | ||||||
| https://<your-domain>/silo/api/github/github-webhook | ||||||
| ``` | ||||||
|
|
||||||
| This allows Plane to receive updates from GitHub repositories. | ||||||
|
|
||||||
|  | ||||||
|
|
||||||
| == GitHub Enterprise Server {#github-enterprise-server} | ||||||
| These steps cover hostname, callback URLs, and private key differences for on‑prem GitHub deployments. | ||||||
| These steps cover hostname, callback URLs, and private key differences for on‑prem GitHub deployments. | ||||||
|
|
||||||
| #### GitHub Enterprise Server | ||||||
| #### GitHub Enterprise Server | ||||||
|
|
||||||
| 1. Go to **Settings \> Developer Settings \> GitHub Apps** in your GitHub organization. | ||||||
| 1. Go to **Settings \> Developer Settings \> GitHub Apps** in your GitHub organization. | ||||||
|
|
||||||
| 2. Click **New GitHub App**. | ||||||
|  | ||||||
| 2. Click **New GitHub App**. | ||||||
|
|
||||||
| 3. In the **Register new GitHub App** page, provide a **GitHub App name** and **Homepage URL**. | ||||||
|  | ||||||
|  | ||||||
|
|
||||||
| 4. In the **Identifying and authorizing users** section, add the following **Callback URLS**. | ||||||
| 3. In the **Register new GitHub App** page, provide a **GitHub App name** and **Homepage URL**. | ||||||
|
|
||||||
| **For Plane cloud instance** | ||||||
|  | ||||||
|
|
||||||
| ```bash | ||||||
| https://silo.plane.so/api/oauth/github-enterprise/auth/callback | ||||||
| https://silo.plane.so/api/oauth/github-enterprise/auth/user/callback | ||||||
| ``` | ||||||
| 4. In the **Identifying and authorizing users** section, add the following **Callback URLS**. | ||||||
|
|
||||||
| **For Plane self-hosted instance** | ||||||
| **For Plane cloud instance** | ||||||
|
|
||||||
| ```bash | ||||||
| https://<your-domain>/silo/api/oauth/github-enterprise/auth/callback | ||||||
| https://<your-domain>/silo/api/oauth/github-enterprise/auth/user/callback | ||||||
| ``` | ||||||
| ```bash | ||||||
| https://silo.plane.so/api/oauth/github-enterprise/auth/callback | ||||||
| https://silo.plane.so/api/oauth/github-enterprise/auth/user/callback | ||||||
| ``` | ||||||
|
|
||||||
| These URLs allow Plane to verify and enable workspace connection with the Github App. | ||||||
|  | ||||||
| :::warning | ||||||
| Make sure to opt out of **Expire user authorization tokens** feature. | ||||||
| ::: | ||||||
| **For Plane self-hosted instance** | ||||||
|
|
||||||
| 5. In the **Post installation** section, add the below **Setup URL**. | ||||||
| ```bash | ||||||
| https://<your-domain>/silo/api/oauth/github-enterprise/auth/callback | ||||||
| https://<your-domain>/silo/api/oauth/github-enterprise/auth/user/callback | ||||||
| ``` | ||||||
|
|
||||||
| **For Plane cloud instance** | ||||||
| These URLs allow Plane to verify and enable workspace connection with the Github App. | ||||||
|
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Correct product name casing: Line 121 should use the official capitalization for consistency and docs quality. - These URLs allow Plane to verify and enable workspace connection with the Github App.
+ These URLs allow Plane to verify and enable workspace connection with the GitHub App.📝 Committable suggestion
Suggested change
🧰 Tools🤖 Prompt for AI Agents |
||||||
|  | ||||||
| :::warning | ||||||
| Make sure to opt out of **Expire user authorization tokens** feature. | ||||||
| ::: | ||||||
|
|
||||||
| ```bash | ||||||
| https://silo.plane.so/api/oauth/github-enterprise/auth/callback | ||||||
| ``` | ||||||
| 5. In the **Post installation** section, add the below **Setup URL**. | ||||||
|
|
||||||
| **For Plane self-hosted instance** | ||||||
| **For Plane cloud instance** | ||||||
|
|
||||||
| ```bash | ||||||
| https://<your-plane-domain>/silo/api/oauth/github-enterprise/auth/callback | ||||||
| ``` | ||||||
| ```bash | ||||||
| https://silo.plane.so/api/oauth/github-enterprise/auth/callback | ||||||
| ``` | ||||||
|
|
||||||
| Redirects users to this URL after GitHub app installation. | ||||||
|  | ||||||
| **For Plane self-hosted instance** | ||||||
|
|
||||||
| 6. Turn on **Redirect on update**. | ||||||
| ```bash | ||||||
| https://<your-plane-domain>/silo/api/oauth/github-enterprise/auth/callback | ||||||
| ``` | ||||||
|
|
||||||
| 7. In the **Webhook** section, add the below **Webhook URL**. | ||||||
| Redirects users to this URL after GitHub app installation. | ||||||
|  | ||||||
|
|
||||||
| **For Plane cloud instance** | ||||||
| 6. Turn on **Redirect on update**. | ||||||
|
|
||||||
| ```bash | ||||||
| https://silo.plane.so/api/github-enterprise/github-webhook | ||||||
| ``` | ||||||
| 7. In the **Webhook** section, add the below **Webhook URL**. | ||||||
|
|
||||||
| **For Plane self-hosted instance** | ||||||
| **For Plane cloud instance** | ||||||
|
|
||||||
| ```bash | ||||||
| https://<your-plane-domain>/silo/api/github-enterprise/github-webhook | ||||||
| ``` | ||||||
| ```bash | ||||||
| https://silo.plane.so/api/github-enterprise/github-webhook | ||||||
| ``` | ||||||
|
|
||||||
| This allows Plane to receive updates from GitHub repositories. | ||||||
| **For Plane self-hosted instance** | ||||||
|
|
||||||
|  | ||||||
| ```bash | ||||||
| https://<your-plane-domain>/silo/api/github-enterprise/github-webhook | ||||||
| ``` | ||||||
|
|
||||||
| This allows Plane to receive updates from GitHub repositories. | ||||||
|
|
||||||
|  | ||||||
|
|
||||||
| ::: | ||||||
|
|
||||||
| ### Set up permissions and events | ||||||
|
|
||||||
| 1. Add repository and account permissions by setting the **Access** dropdown next to each permission, as shown in the tables below. | ||||||
|
|
||||||
|  | ||||||
|
|
||||||
| **Repository permissions** | ||||||
|
|
||||||
| Original file line number | Diff line number | Diff line change | ||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
|
@@ -41,6 +41,10 @@ Supported models: | |||||||||||||||||||||
|
|
||||||||||||||||||||||
| You can provide API keys for both OpenAI and Anthropic, making all models available to users. If you provide only one key, users will only have access to that provider's models. | ||||||||||||||||||||||
|
|
||||||||||||||||||||||
| :::tip | ||||||||||||||||||||||
| If you need to use an LLM that isn't from OpenAI or Anthropic — for example, an open-source model or a regional provider for compliance reasons — you can proxy it through [LiteLLM](https://docs.litellm.ai). LiteLLM exposes any LLM behind an OpenAI-compatible API, which Plane can then connect to using the `CUSTOM_LLM_*` variables with `CUSTOM_LLM_PROVIDER=openai`. | ||||||||||||||||||||||
| ::: | ||||||||||||||||||||||
|
Comment on lines
+44
to
+46
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Wrap the tip text to keep markdown within formatting limits. Line 45 is far beyond the configured markdown line width and is likely to fail/prevent consistent Prettier formatting. 💡 Proposed formatting fix :::tip
-If you need to use an LLM that isn't from OpenAI or Anthropic — for example, an open-source model or a regional provider for compliance reasons — you can proxy it through [LiteLLM](https://docs.litellm.ai). LiteLLM exposes any LLM behind an OpenAI-compatible API, which Plane can then connect to using the `CUSTOM_LLM_*` variables with `CUSTOM_LLM_PROVIDER=openai`.
+If you need to use an LLM that isn't from OpenAI or Anthropic — for example,
+an open-source model or a regional provider for compliance reasons — you can
+proxy it through [LiteLLM](https://docs.litellm.ai). LiteLLM exposes any LLM
+behind an OpenAI-compatible API, which Plane can then connect to using the
+`CUSTOM_LLM_*` variables with `CUSTOM_LLM_PROVIDER=openai`.
:::As per coding guidelines, " 📝 Committable suggestion
Suggested change
🤖 Prompt for AI Agents |
||||||||||||||||||||||
|
|
||||||||||||||||||||||
| #### Custom models (self-hosted or third-party) | ||||||||||||||||||||||
|
|
||||||||||||||||||||||
| Plane AI supports custom models through two backends: | ||||||||||||||||||||||
|
|
@@ -51,7 +55,7 @@ Plane AI supports custom models through two backends: | |||||||||||||||||||||
| One custom model can be configured alongside your public provider keys. | ||||||||||||||||||||||
|
|
||||||||||||||||||||||
| ::: warning | ||||||||||||||||||||||
| The custom model should have at least 100 billion parameters for all Plane AI features to work reliably. Larger, more capable models yield better results. | ||||||||||||||||||||||
| The custom model should have at least 1 trillion parameters for all Plane AI features to work reliably. Larger, more capable models yield better results. | ||||||||||||||||||||||
| ::: | ||||||||||||||||||||||
|
|
||||||||||||||||||||||
| ### Embedding models | ||||||||||||||||||||||
|
|
||||||||||||||||||||||

Uh oh!
There was an error while loading. Please reload this page.