Skip to content
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

feat: add logseq-block-to-page-next plugin #455

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

b-yp
Copy link
Contributor

@b-yp b-yp commented Oct 6, 2023

Submit a new Plugin to Marketplace

Plugin Github repo URL: https://github.com/b-yp/logseq-plugin-block-to-page

Github releases checklist

  • a legal package.json file.
  • a valid CI workflow build action for Github releases. (theme plugin for this).
  • a release which includes a release zip pkg from a successful build.
  • a clear README file, ideally with an image or gif showcase. (For more friendly to users, it is recommended to have English version description).
  • a license in the LICENSE file.

@b-yp
Copy link
Contributor Author

b-yp commented Oct 6, 2023

The plugin is forked from https://github.com/hyrijk/logseq-plugin-block-to-page, but the original plugin author no longer maintains it, so I would like to fork over to continue maintenance

@yoyurec
Copy link
Contributor

yoyurec commented Oct 6, 2023

@b-yp why not just ask the author to add you as co-owner?
or even transfer the original repo to your account to become the full owner?

@xyhp915
Copy link
Collaborator

xyhp915 commented Oct 7, 2023

@b-yp why not just ask the author to add you as co-owner? or even transfer the original repo to your account to become the full owner?

Hi @b-yp I think this is a good suggestion. In this way, the ID of the plug-in does not need to be adjusted. Of course, if it is confirmed that the author of the original plug-in repo is no longer maintained (such as Archived status), then it is also feasible to directly link the plug-in repo URL to your repository.

@b-yp
Copy link
Contributor Author

b-yp commented Oct 7, 2023

Thank you both for your suggestions. I will communicate with the original developer.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants