[FR]: custom "Key::Value" as trigger to publish about obsidian-github-publisher HOT 5 CLOSED

For the github repository, I thinked about that when I first developped the fonction, and abandon the idea because it have the exact same limit of the actual fonction, and need more overwork to just create a key/value. The actual behavior is « okay » for me.

Also, if you have many project connected to different repo, I think it's better to use another vault for that, than the plugin.

For the other suggestion, adding this function necessite a lot of rework, as many many function are linked to if frontmatter[sharekey].
If I create this, I need to create another function, that will check the key.... For something I don't see the interest.

If you need to add another key for your repository & the sharing key, you could use linter, metadata-menu, and quickadd. Or, check with VSCode or other IDE to add the key.
Don't forget that to send to another repo, you need to use
repo: user/repo/branch (or just : repo: repo if the repo is on your own github)

from obsidian-github-publisher.

working in multiple vaults is sub-par in my view as they can not share info. and some of the project related info needs to be shared (contact information for example of people working on multiple projects) or references to previous accomplishements ...

i get that my "needs" are apparently very unique ... and i am really struggling to get them untangled. :)

there will be a solution - i am sure

thanks for the fast response.

from obsidian-github-publisher.

Why don't you remove the frontmatter key using the regex replacement? You can use the function to run it after the other conversion

from obsidian-github-publisher.

Hello!
I changed my mind after some times and develop in #add-multiple-repo the possibility to set shortRepo, and allowing to set commands & everything to more than one repo!
I know it's not 100% the thing you want, but now you can remove regex & all if you want to use multiple repo!

from obsidian-github-publisher.

wow! thanks for the update - this is amazing news! i must admit i fell off the obsidian wagon a bit because we had to switch to a more team- based collaboration tool (in this case clickup) but having this could be a gamechanger. thanks

from obsidian-github-publisher.