Skip to content

Conversation

@Feng6611
Copy link
Contributor

@Feng6611 Feng6611 commented Oct 15, 2025

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/Feng6611/Obsidian-open-in-Teminal

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 (optional)
  • GitHub release name matches the exact version number specified in my manifest.json (Note: Use the exact version number, don't include a prefix v)
  • 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.

@ObsidianReviewBot
Copy link
Collaborator

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

Required

[1][2]:This is only available on desktop, use the Platform interface from the Obsidian API instead.


Do NOT open a new PR for re-validation.
Once you have pushed all of the required changes to your repo, the bot will update the labels on this PR 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.

@ObsidianReviewBot ObsidianReviewBot added Changes requested Additional review required PR needs to be reviewed by another person, after the currently requested changes have been made Ready for review and removed Ready for review Changes requested Additional review required PR needs to be reviewed by another person, after the currently requested changes have been made labels Oct 16, 2025
@ObsidianReviewBot ObsidianReviewBot removed their assignment Oct 17, 2025
@ObsidianReviewBot
Copy link
Collaborator

Changes requested by bot have been made, ready 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.

@github-actions
Copy link

Hello!

I found the following issues in your plugin submission

Errors:

❌ Could not parse community-plugins.json, invalid JSON. Expected ',' or ']' after array element in JSON at position 627938


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

The automated review has not found any issues with your code, ready for manual review.
Please be aware that it might take a few weeks before your plugin is reviewed due to the high volume of submissions currently.

@ObsidianReviewBot
Copy link
Collaborator

The automated review has not found any issues with your code, ready for manual review.
Please be aware that it might take a few weeks before your plugin is reviewed due to the high volume of submissions currently.

@claremacrae
Copy link
Contributor

I'm a bit confused as to why the PR is called 'Open in Terminal' but the repo is called 'Obsidian-File-Ignore'.

What am I misunderstanding?

@Feng6611
Copy link
Contributor Author

I'm a bit confused as to why the PR is called 'Open in Terminal' but the repo is called 'Obsidian-File-Ignore'.

What am I misunderstanding?

I'm sorry about it, I have update it. URL https://github.com/Feng6611/Obsidian-open-in-Teminal

@claremacrae
Copy link
Contributor

Great - thanks.

@claremacrae
Copy link
Contributor

Hi, in case it helps, just to let you know, you don’t need to keep merging new cookies into this PR.

The Obsidian team will take care of that when the PR is eventually merged.

@ObsidianReviewBot ObsidianReviewBot removed their assignment Oct 26, 2025
@ObsidianReviewBot
Copy link
Collaborator

The automated review has not found any issues with your code, ready for manual review.
Please be aware that it might take a few weeks before your plugin is reviewed due to the high volume of submissions currently.

@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 Nov 4, 2025
@ObsidianReviewBot ObsidianReviewBot self-assigned this Nov 4, 2025
@ObsidianReviewBot
Copy link
Collaborator

Required

[1]
Unexpected console statement. Only these console methods are allowed: warn, error, debug.

[1][2][3][4][5][6]
Unnecessary escape character: ".

[1][2][3]
For a consistent UI use new Setting(containerEl).setName(...).setHeading() instead of creating HTML heading elements directly.

[1][2]
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.

@Feng6611
Copy link
Contributor Author

Feng6611 commented Nov 4, 2025

Required

[1] Unexpected console statement. Only these console methods are allowed: warn, error, debug.

[1][2][3][4][5][6] Unnecessary escape character: ".

[1][2][3] For a consistent UI use new Setting(containerEl).setName(...).setHeading() instead of creating HTML heading elements directly.

[1][2] 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.

I have fixed this issue. @ObsidianReviewBot

@github-actions github-actions bot added the Skipped code scan Code scanning skipped because submission is not in TS/author believes result is wrong label Nov 4, 2025
@Feng6611
Copy link
Contributor Author

Feng6611 commented Nov 5, 2025

hello, I fixed issues. But I dont know what happened about the label "skip", Plz help me @claremacrae

@claremacrae
Copy link
Contributor

Hi, I’ve asked on Discord - will let you know if there is a useful answer.

@joethei joethei removed the Skipped code scan Code scanning skipped because submission is not in TS/author believes result is wrong label Nov 5, 2025
@claremacrae
Copy link
Contributor

Here's the start of the discussion in Discord:
https://discord.com/channels/686053708261228577/840286264964022302/1435522465420935242

I see someone from the Obsidian team how now removed the 'Skipped code scan' label manually.

@ObsidianReviewBot
Copy link
Collaborator

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

Required

[1]
Avoid including the plugin name in settings headings.

[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.

1 similar comment
@ObsidianReviewBot
Copy link
Collaborator

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

Required

[1]
Avoid including the plugin name in settings headings.

[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.

@ObsidianReviewBot
Copy link
Collaborator

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

Required

[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.

1 similar comment
@ObsidianReviewBot
Copy link
Collaborator

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

Required

[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.

@ObsidianReviewBot ObsidianReviewBot removed their assignment Nov 9, 2025
@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 Nov 9, 2025
@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.

4 participants