Skip to content

Conversation

@ran-codes
Copy link

@ran-codes ran-codes commented Jan 29, 2026

I am submitting a new Community Plugin

  • I attest that I have done my best to deliver a high-quality plugin, am proud of the code I have written, and would recommend it to others. I commit to maintaining the plugin and being responsive to bug reports. If I am no longer able to maintain it, I will make reasonable efforts to find a successor maintainer or withdraw the plugin from the directory.

Repo URL

Link to my plugin: https://github.com/ran-codes/obsidian-integrated-terminal

Release Checklist

  • I have tested the plugin on
    • Windows
    • macOS
    • Linux
    • Android (if applicable)
    • iOS (if applicable)
  • My GitHub release contains all required files (as individual files, not just in the source.zip / source.tar.gz)
    • main.js
    • manifest.json
    • styles.css
  • GitHub release name matches the exact version number specified in my manifest.json
  • The id in my manifest.json matches the id in the community-plugins.json file.
  • My README.md describes the plugin's purpose and provides clear usage instructions.
  • I have read the developer policies at https://docs.obsidian.md/Developer+policies, and have assessed my plugin's adherence to these policies.
  • I have read the tips in https://docs.obsidian.md/Plugins/Releasing/Plugin+guidelines and have self-reviewed my plugin to avoid these common pitfalls.
  • I have added a license in the LICENSE file.
  • My project respects and is compatible with the original license of any code from other plugins that I'm using.
    I have given proper attribution to these other projects in my README.md.

Copilot AI review requested due to automatic review settings January 29, 2026 23:22
@github-actions
Copy link

Hello!

I found the following issues in your plugin submission

Errors:

❌ You did not follow the pull request template. The PR template can be found here
❌ Please don't include Obsidian in the plugin description
❌ Unable to find a release with the tag 0.0.1. Make sure that the version in your manifest.json file in your repo points to the correct Github Release.


This check was done automatically. Do NOT open a new PR for re-validation. Instead, to trigger this check again, make a change to your PR and wait a few minutes, or close and re-open it.

Copy link

Copilot AI left a comment

Choose a reason for hiding this comment

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

Pull request overview

This pull request adds a new community plugin entry for "Integrated Terminal" to the community plugins registry.

Changes:

  • Adds a new plugin entry with id "integrated-terminal", authored by ran-li, describing a lightweight integrated terminal for Obsidian.

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

Comment on lines 19043 to 19047
"id": "integrated-terminal",
"name": "Integrated Terminal",
"author": "ran-li",
"description": "Lightweight integrated terminal for Obsidian.",
"repo": "ran-codes/obsidian-integrated-terminal"
Copy link

Copilot AI Jan 29, 2026

Choose a reason for hiding this comment

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

The indentation for this new plugin entry is inconsistent with the rest of the file. The file consistently uses 4 spaces for object properties, but this entry uses 6 spaces. Please adjust the indentation to use 4 spaces for each property to match the existing formatting pattern.

Copilot uses AI. Check for mistakes.
@github-actions
Copy link

Hello!

I found the following issues in your plugin submission

Errors:

❌ You did not follow the pull request template. The PR template can be found here
❌ Description mismatch, the description in this PR (Lightweight integrated terminal embedded directly in your workspace.) is not the same as the one in your repo (Lightweight integrated terminal for Obsidian.). If you just changed it, remember to change it in the manifest.json in your repo and your latest GitHub release.


This check was done automatically. Do NOT open a new PR for re-validation. Instead, to trigger this check again, make a change to your PR and wait a few minutes, or close and re-open it.

@ran-codes ran-codes closed this Jan 29, 2026
@ran-codes ran-codes reopened this Jan 29, 2026
@github-actions github-actions bot changed the title Add Integrated Terminal plugin details Add plugin: Integrated Terminal Jan 29, 2026
@ObsidianReviewBot ObsidianReviewBot added Changes requested Additional review required PR needs to be reviewed by another person, after the currently requested changes have been made and removed Ready for review labels Jan 29, 2026
@ObsidianReviewBot
Copy link
Collaborator

Thank you for your submission, an automated scan of your plugin code's revealed the following issues:

Required

[1][2][3][4][5][6][7][8][9][10][11]
Promises must be awaited, end with a call to .catch, end with a call to .then with a rejection handler or be explicitly marked as ignored with the void operator.

[1][2]
Promise returned in function argument where a void return was expected.

[1][2][3][4][5][6][7][8]
Unexpected any. Specify a different type.

[1][2][3][4][5]
A require() style import is forbidden.

[1][2]
Async method 'onClose' has no 'await' expression.

[1][2]
Use sentence case for UI text.

[1]
Don't provide a default hotkey, as they might conflict with other hotkeys the user has already set, or that are included with Obsidian by default.

[1]
Promise-returning method provided where a void return was expected by extended/implemented type 'Plugin'.

[1]
Async method 'onunload' has no 'await' expression.

[1]
This assertion is unnecessary since it does not change the type of the expression.

[1][2]
Avoid setting styles directly via element.style.display. Use CSS classes for better theming and maintainability. Use the setCssProps function to change CSS properties.

[1]
Avoid setting styles directly via element.style.width. Use CSS classes for better theming and maintainability. Use the setCssProps function to change CSS properties.

[1]
Avoid setting styles directly via element.style.marginBottom. Use CSS classes for better theming and maintainability. Use the setCssProps function to change CSS properties.

[1]
Async method 'onOpen' has no 'await' expression.


Optional


Do NOT open a new PR for re-validation.
Once you have pushed some changes to your repository the bot will rescan within 6 hours
If you think some of the required changes are incorrect, please comment with /skip and the reason why you think the results are incorrect.
To run these checks locally, install the eslint plugin in your project.
Do NOT rebase this PR, this will be handled by the reviewer once the plugin has been approved.

@github-actions
Copy link

Hello!

I found the following issues in your plugin submission

Errors:

❌ Description mismatch, the description in this PR (Lightweight integrated terminal embedded directly in your workspace.) is not the same as the one in your repo (Lightweight integrated terminal for obsidian.). If you just changed it, remember to change it in the manifest.json in your repo and your latest GitHub release.


This check was done automatically. Do NOT open a new PR for re-validation. Instead, to trigger this check again, make a change to your PR and wait a few minutes, or close and re-open it.

@github-actions
Copy link

Hello!

I found the following issues in your plugin submission

Errors:

❌ Please don't include Obsidian in the plugin description


This check was done automatically. Do NOT open a new PR for re-validation. Instead, to trigger this check again, make a change to your PR and wait a few minutes, or close and re-open it.

@ObsidianReviewBot
Copy link
Collaborator

Thank you for your submission, an automated scan of your plugin code's revealed the following issues:

Required

[1]
Avoid casting to 'TFile'. Use an 'instanceof TFile' check to safely narrow the type.

[1]
This assertion is unnecessary since it does not change the type of the expression.

[1]
Use sentence case for UI text.


Optional


Do NOT open a new PR for re-validation.
Once you have pushed some changes to your repository the bot will rescan within 6 hours
If you think some of the required changes are incorrect, please comment with /skip and the reason why you think the results are incorrect.
To run these checks locally, install the eslint plugin in your project.
Do NOT rebase this PR, this will be handled by the reviewer once the plugin has been approved.

@ran-codes ran-codes closed this Feb 2, 2026
@ran-codes ran-codes reopened this Feb 2, 2026
@ObsidianReviewBot ObsidianReviewBot removed their assignment Feb 2, 2026
@ObsidianReviewBot ObsidianReviewBot added Ready for review and removed Changes requested Additional review required PR needs to be reviewed by another person, after the currently requested changes have been made labels Feb 2, 2026
@ObsidianReviewBot
Copy link
Collaborator

Changes requested by bot have been made, ready for for additional review by human.
Please be aware that it might take a few weeks before your plugin is reviewed due to the high volume of submissions currently.
Any changes you make to your repository will be automatically reviewed by the bot.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants