Skip to content

Add plugin: Geocode Note#11960

Open
blamouche wants to merge 1 commit intoobsidianmd:masterfrom
blamouche:patch-1
Open

Add plugin: Geocode Note#11960
blamouche wants to merge 1 commit intoobsidianmd:masterfrom
blamouche:patch-1

Conversation

@blamouche
Copy link
Copy Markdown

@blamouche blamouche commented Apr 14, 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/blamouche/obsidian-geocode-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'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.

Add geographic metadata (coordinates, icon, color) to notes. Supports device geolocation, address search via OpenStreetMap, and manual entry. Writes to YAML frontmatter for compatibility with map plugins like Map View.
@github-actions
Copy link
Copy Markdown

Hello!

I found the following issues in your plugin submission

Errors:

❌ Unable to find a release with the tag 1.0.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.

@blamouche blamouche closed this Apr 14, 2026
@blamouche blamouche reopened this Apr 14, 2026
@github-actions github-actions bot changed the title Add Geocode Note plugin information Add plugin: Geocode Note Apr 14, 2026
@blamouche
Copy link
Copy Markdown
Author

Test done on IOS, working well

@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 Apr 15, 2026
@ObsidianReviewBot
Copy link
Copy Markdown
Collaborator

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

Required

[1][2][3]
Promise returned in function argument where a void return was expected.

[1]
Promises must be awaited, end with a call to .catch, end with a call to .then with a rejection handler or be explicitly marked as ignored with the void operator.

[1]
Async method 'onload' has no 'await' expression.


Optional

[1]
'Setting' is defined but never used.


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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Additional review required PR needs to be reviewed by another person, after the currently requested changes have been made Changes requested plugin

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants