-
Notifications
You must be signed in to change notification settings - Fork 3
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
How to install, given new ownership? #2
Comments
Yep, this question was going to pop up soon. We need to migrate the issues and maybe create a sort of GitHub action to build the release. I don't think there'll be a clear way to point from that repo to this but I may be wrong. |
Could you maybe clarify the status of that fork in the readme or in a discord post ? Is this fork a personal thing, or a collective action ? (I think I remember 6 months ago a group of active users waiting for Olivier Balfour'a answer about his plugin). Should we copy paste the pending issues from the original repo ? Should we amend Obsidian's plugin list to point out to that new and updated repo ?... |
You're right. I'll try and prioritize that status and how-to at the very least. Issue migration and other updates will take a bit longer. |
Hi guys, has there been an update on this? Just curious :) Thanks! |
Sorry, this has fallen down the pecking order. Currently, this can be installed via the BRAT plugin I believe. |
Can you maybe clarify on the BRAT installation process? If I paste the repo's URL in BRAT I get an error message, saying the file "main.js" is missing. As far as I can tell, the "main.js" will be included in a release version (aka will be build for that release?). I'm fairly new to using github and obsidian. Is there a way to "build" the release on my own? The BRAT process worked for the fork of Phillip Johnston (https://github.com/phillipjohnston/obsidian-pandoc), which has a release. |
You're right, this repo doesn't have a release. Continue to use Philip's fork but let me try setting up a GH action to automatically build a release. On a separate note, @phillipjohnston, do you think you we can merge some of your improvements and push out a release? |
I'll actually go ahead and create a release manually for now. |
@AB1908 changes were merged in with a PR already. |
Ah, I guess I should've checked. Thanks! |
The fork here is a little confusing. I understand why it exists, but is this codebase now where the Community plugins UI is pulling from, or do I need to manually install this version?
I think if this switch is happening, it should probably fully happen, ie. the community plugins should point to this repo, the readme links should be updated to point here instead of at the old repo, etc.
If this is welcome I can probably do this myself and submit a PR, but I want to coordinate about it first.
The text was updated successfully, but these errors were encountered: