langgenius/dify-plugins
1
0
Fork 0
mirror of https://github.com/langgenius/dify-plugins.git synced 2026-07-22 01:55:36 -04:00
Code Issues 119 Packages Projects Releases Wiki Activity

Add a link to the repository for the each plugin on the marketplace. #7

New Issue
Closed
opened 2026-02-22 17:15:30 -05:00 by yindo · 4 comments
yindo commented 2026-02-22 17:15:30 -05:00
Owner
Copy Link
Copy Source

Originally created by @kurokobo on GitHub (Mar 8, 2025).

Originally assigned to: @RockChinQ on GitHub.

This is a feature request for the marketplace.

I would like to have a link to the repository that manages its source code on the page for each plugin.

Currently, it is possible to check the source code by downloading it, changing the extension to zip, and then extracting it. However, having a link to the repository on each plugin pages on the marketplace offers the following advantages:

  • It becomes easier to check the source code, including past versions by using tags / releases.
  • Bug reports and contributions can be made for each plugin.

From a technical perspective, I have considered the following ideas. What do you think?

  • Add keys to the plugin manifest to store the official site or repository URL (not mandatory)
  • If the keys exist for the plugin, display links on the plugin page in the marketplace.

It's just like this part of PyPI.

Image

Originally created by @kurokobo on GitHub (Mar 8, 2025). Originally assigned to: @RockChinQ on GitHub. This is a feature request for the marketplace. I would like to have a link to the repository that manages its source code on the page for each plugin. Currently, it is possible to check the source code by downloading it, changing the extension to zip, and then extracting it. However, having a link to the repository on each plugin pages on the marketplace offers the following advantages: - It becomes easier to check the source code, including past versions by using tags / releases. - Bug reports and contributions can be made for each plugin. From a technical perspective, I have considered the following ideas. What do you think? - [ ] Add keys to the plugin manifest to store the official site or repository URL (not mandatory) - [ ] If the keys exist for the plugin, display links on the plugin page in the marketplace. It's just like this part of PyPI. ![Image](https://github.com/user-attachments/assets/6fd13a84-ea4f-4253-835f-f425c3c7f12d)
yindo closed this issue 2026-02-22 17:15:30 -05:00
yindo commented 2026-02-22 17:15:30 -05:00
Author
Owner
Copy Link
Copy Source

@bowenliang123 commented on GitHub (Mar 13, 2025):

+1
As in all my pulished plugins at Dify Marketplace (https://marketplace.dify.ai/plugins/bowenliang123/md_exporter), I attached the links to the github repo.

Image

And it does help the user to know more about the details of the plugin and report the usage issues they've encountered. As in my md_exporter plugin, 2 helpful issues collected which are helpful for me to follow.

@bowenliang123 commented on GitHub (Mar 13, 2025): +1 As in all my pulished plugins at Dify Marketplace (https://marketplace.dify.ai/plugins/bowenliang123/md_exporter), I attached the links to the github repo. <img width="669" alt="Image" src="https://github.com/user-attachments/assets/d2c1e17d-3dca-48ff-93c0-445e84464ca2" /> And it does help the user to know more about the details of the plugin and report the usage issues they've encountered. As in my `md_exporter` plugin, 2 helpful issues collected which are helpful for me to follow.
yindo commented 2026-02-22 17:15:30 -05:00
Author
Owner
Copy Link
Copy Source

@alterxyz commented on GitHub (Mar 15, 2025):

+1

@alterxyz commented on GitHub (Mar 15, 2025): +1
yindo commented 2026-02-22 17:15:30 -05:00
Author
Owner
Copy Link
Copy Source

@kurokobo commented on GitHub (May 7, 2025):

Related PRs by @Yeuoly:

@kurokobo commented on GitHub (May 7, 2025): Related PRs by @Yeuoly: - https://github.com/langgenius/dify-plugin-daemon/pull/262 - https://github.com/langgenius/dify-plugin-sdks/pull/134 - https://github.com/langgenius/dify/pull/19337
yindo commented 2026-02-22 17:15:30 -05:00
Author
Owner
Copy Link
Copy Source

@RockChinQ commented on GitHub (Jun 24, 2025):

Any new uploaded plugin versions with the repo field set in manifest.yaml will now be displayed on the Marketplace.

Image

@RockChinQ commented on GitHub (Jun 24, 2025): Any new uploaded plugin versions with the `repo` field set in `manifest.yaml` will now be displayed on the Marketplace. ![Image](https://github.com/user-attachments/assets/b64c565d-3757-43ec-9906-6b95c7c28449)
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
Plugin Request
Plugin Request
Plugin Request
bug
duplicate
enhancement
pull-request
Mirrored from GitHub Pull Request
 question
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
yindo
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: langgenius/dify-plugins#7
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?