Skip to content

Conversation

@Lyqed
Copy link

@Lyqed Lyqed commented Jan 30, 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/Lyqed/copy-as-note

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\x27t 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\x27s purpose and provides clear usage instructions.
  • I have read the developer policies at https://docs.obsidian.md/Developer+policies, and have assessed my plugin\x27s 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\x27m using.
    I have given proper attribution to these other projects in my README.md.

@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
❌ Your manifest has the invalid main property.


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.

@Lyqed
Copy link
Author

Lyqed commented Jan 30, 2026

Updated PR description to follow the plugin submission template and updated the repo manifest to remove the disallowed main key. Also re-uploaded manifest.json to the existing 1.0.0 release.

@Lyqed
Copy link
Author

Lyqed commented Jan 30, 2026

/rerun

@Lyqed
Copy link
Author

Lyqed commented Jan 30, 2026

Updated PR body to match the official plugin PR template (via --body-file) and removed the disallowed key from manifest.json (also re-uploaded manifest.json to release 1.0.0). Please re-run validation.

@Lyqed
Copy link
Author

Lyqed commented Jan 30, 2026

/rerun

@Lyqed
Copy link
Author

Lyqed commented Jan 30, 2026

Closing and reopening to trigger validation after updating PR body and plugin manifest/release assets.

@Lyqed Lyqed closed this Jan 30, 2026
@Lyqed Lyqed reopened this Jan 30, 2026
@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


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