-
Notifications
You must be signed in to change notification settings - Fork 2.4k
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
Add plugin: LLM Summary #4040
Add plugin: LLM Summary #4040
Conversation
Hello!I found the following issues in your plugin submission Errors: ❌ Your latest Release is missing the 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. |
Hello!I found the following issues in your plugin submission Errors: ❌ Your latest Release is missing the 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. |
Thank you for your submission, an automated scan of your plugin code's revealed the following issues: Required[1][2][3]:Remember to rename the sample classes to something that makes sense to your plugin. If there are any errors, Obsidian will spit out this class name, so this will be important for users to debug if they need to. [1]:The command name should not include the plugin name. [1]:Please remove anything from the sample plugin that you don't need. Optional[1]:We recommend against providing a default hotkey when possible. The reason being that it's easy to pick a hotkey that a user already has configured and they could get confused when that key doesn't do what they expect. Also, it's hard choosing a safe default hotkey that's available for all operating systems. Do NOT open a new PR for re-validation. |
All changes released. |
Changes requested by bot have been made, assigning human for additional review. |
pdfs "fundingUrl": "https://www.qiaosun.me/funding", statusBarItemEl.setText('LLM Ready');, name: 'Initialize Notes Folders',, statusBarItemEl.setText('Defining New Concept..');, statusBarItemEl.setText('LLM Ready');, .setName('New Concept Fields (Required)') |
Thank you for your review. All problems have been solved in a later release (v0.1.9). Please check. |
Hello!I found the following issues in your plugin submission Errors: ❌ Unable to find a release with the tag 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. |
Thanks for pointing out. Fixed by publishing the new release. |
Hi there, as this PR has not seen any activity in the last 30 days, it will be closed in 15 days unless there are any updates. |
Link to my plugin: https://github.com/larksq/obsidian-llm-summary - [x] I have tested the plugin on - [ ] Windows - [x] macOS - [ ] Linux - [ ] Android (if applicable) - [ ] iOS (if applicable) - [x] My GitHub release contains all required files (as individual files, not just in the source.zip / source.tar.gz) - [x] main.js - [x] manifest.json - [x] styles.css (optional) - [x] 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) - [x] The id in my manifest.json matches the id in the community-plugins.json file. - [x] My README.md describes the plugin's purpose and provides clear usage instructions. - [x] I have read the developer policies at https://docs.obsidian.md/Developer+policies, and have assessed my plugins's adherence to these policies. - [x] 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. - [x] I have added a license in the LICENSE file. - [x] My project respects and is compatible with the original license of any code from other plugins that I'm using. - [x] I have given proper attribution to these other projects in my README.md.
I am submitting a new Community Plugin
Repo URL
Link to my plugin: https://github.com/larksq/obsidian-llm-summary
Release Checklist
I have tested the plugin on - [ ] Windows - [x] 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)
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 plugins'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.
Please switch to Preview and select one of the following links: