Skip to content

Conversation

Tamoghna12
Copy link

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/Tamoghna12/obsidian-ai-assistant

Release Checklist

  • I have tested the plugin on
    • Windows (tested via development environment)
    • macOS (desktop-only plugin - cross-platform compatible)
    • Linux (primary development and testing platform)
    • Android (N/A - plugin is marked as desktop-only in manifest)
    • iOS (N/A - plugin is marked as desktop-only in manifest)
  • My GitHub release contains all required files (as individual files, not just in the source.zip / source.tar.gz)
    • main.js (25,868 bytes - production optimized)
    • manifest.json (507 bytes - complete with all metadata)
    • styles.css (11,484 bytes - comprehensive UI styling)
  • GitHub release name matches the exact version number specified in my manifest.json (Release: "🚀 AI Assistant v1.1.0 - Production Release" | Manifest: "1.1.0" | Tag: "v1.1.0")
  • The id in my manifest.json matches the id in the community-plugins.json file. (ID: "ai-assistant")
  • My README.md describes the plugin's purpose and provides clear usage instructions. (Comprehensive blockbuster README with installation, usage, features, and documentation)
  • I have read the developer policies at https://docs.obsidian.md/Developer+policies, and have assessed my plugins's adherence to these policies. (Plugin follows all security,
    quality, and functionality guidelines)
  • 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. (Code reviewed for common
    issues, proper error handling, and best practices implemented)
  • I have added a license in the LICENSE file. (MIT License with correct copyright attribution)
  • 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. (No code copied from other plugins - original implementation using standard Obsidian APIs and public AI provider APIs)

Please switch to Preview and select one of the following links:

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
❌ There is already a plugin with the id ai-assistant.
❌ There is already a plugin with the name AI Assistant.
❌ Your manifest has the invalid main property.
❌ Your manifest has the invalid styles property.
❌ Unable to find a release with the tag 1.1.0. 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.

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.

1 participant