Skip to content

Conversation

@dbarnett
Copy link
Contributor

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/dbarnett/obsidian-gh-links-shortener

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

@github-actions
Copy link

Hello!

I found the following issues in your plugin submission

Errors:

❌ Plugin name mismatch, the name in this PR (GH links shortener) is not the same as the one in your repo (GH Links Shortener). If you just changed your plugin name, remember to change it in the manifest.json in your repo and your latest GitHub release.
❌ Unable to find a release with the tag 0.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.

@github-actions github-actions bot changed the title Add plugin: gh-links-shortener Add plugin: GH Links Shortener Aug 19, 2025
@ObsidianReviewBot ObsidianReviewBot removed their assignment Aug 20, 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.

@Zachatoo Zachatoo self-assigned this Oct 30, 2025
@Zachatoo
Copy link
Collaborator

# Obsidian GH Links Shortener Plugin
Naming something "Obsidian xyz" is reserved for first party products we create, please change this header.

Please remove the styles.css file from your repo if you aren't using it.

@Zachatoo Zachatoo added Changes requested Minor changes requested PR can be merged after some final changes have been requested and removed Ready for review labels Oct 30, 2025
@dbarnett
Copy link
Contributor Author

Yay thank you for reviewing my submission!!

You're referring only to the name in the README heading, right, no concerns in manifest or anything?

Later today I'll remove styles.css and also fix package.json which I saw still has some placeholder names.

@dbarnett
Copy link
Contributor Author

K, updated!

I don't think any of that actually affected any actual contents on the Release itself, but if needed LMK and I can bump the release version for that.

@ObsidianReviewBot ObsidianReviewBot added Ready for review Changes made and removed Changes requested Minor changes requested PR can be merged after some final changes have been requested labels Oct 31, 2025
@Zachatoo
Copy link
Collaborator

Zachatoo commented Nov 1, 2025

Right, your manifest.json file was fine. And right again, no new release needed!

@Zachatoo Zachatoo merged commit 557ca9d into obsidianmd:master Nov 1, 2025
1 check passed
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.

3 participants