Hi, I created a new plugin et created a pull request.
master
← elekis-git:master
opened 04:40PM - 02 May 25 UTC
# I am submitting a new Community Plugin
## Repo URL
Link to my plugin: … https://github.com/elekis-git/obsidian-properties-view
## Release Checklist
- [ ] I have tested the plugin on
- [X] Windows
- [X] macOS
- [X] 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.
I have given proper attribution to these other projects in my `README.md`.
Question, must I have to do something else. As it’s the first time I do a PR, dunno if everything is ok or not. There are no button, no step, etc… (and the first one was bad, had to cancel).
thanks.
resolve the issues in your code on your part and wait for the team to pull your code.
Again this message. One week ago I had nothing.
I tried to resolve but now I have this message
This branch cannot be rebased due to conflicts
Changes can be cleanly merged.
And I cant do nothing. I m tired about that (3rd time). the plugin is there for people who want. Releases · elekis-git/obsidian-properties-view · GitHub
thanks.
Ignore the merge conflict, we will handle that when merging.
Please don’t open a new PR, that will only send you back to the beginning of the queue.