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

[PR #567] [MERGED] Add plugin migege/markdown2html #1031

New Issue
Closed
opened 2026-02-22 17:45:40 -05:00 by yindo · 0 comments
yindo commented 2026-02-22 17:45:40 -05:00
Owner
Copy Link
Copy Source

📋 Pull Request Information

Original PR: https://github.com/langgenius/dify-plugins/pull/567
Author: @migege
Created: 5/27/2025
Status: ✅ Merged
Merged: 6/3/2025
Merged by: @LogicOber

Base: main ← Head: main

📝 Commits (4)

  • fbf5fdc migege/markdown2html added
  • 6dfd427 migege/markdown2html added and README updated
  • c9a5241 Merge branch 'langgenius:main' into main
  • b1ce673 icon changed, i18n texts changed

📊 Changes

1 file changed (+0 additions, -0 deletions)

View changed files

➕ migege/markdown2html.difypkg (+0 -0)

📄 Description

Plugin Submission Form

1. Metadata

2. Submission Type

  • New plugin submission
  • Version update for existing plugin

3. Description

Markdown2HTML will act as a tool node for Dify to convert Markdown text into HTML without writing to a file.

4. Checklist

  • I have read and followed the Publish to Dify Marketplace guidelines
  • I have read and comply with the Plugin Developer Agreement
  • I confirm my plugin works properly on both Dify Community Edition and Cloud Version
  • I confirm my plugin has been thoroughly tested for completeness and functionality
  • My plugin brings new value to Dify

5. Documentation Checklist

Please confirm that your plugin README includes all necessary information:

  • Step-by-step setup instructions
  • Detailed usage instructions
  • All required APIs and credentials are clearly listed
  • Connection requirements and configuration details
  • Link to the repository for the plugin source code

6. Privacy Protection Information

Based on Dify Plugin Privacy Protection Guidelines:

Data Collection

Markdown2HTML does not collect any user personal data.

Privacy Policy

  • I confirm that I have prepared and included a privacy policy in my plugin package based on the Plugin Privacy Protection Guidelines

🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.

## 📋 Pull Request Information **Original PR:** https://github.com/langgenius/dify-plugins/pull/567 **Author:** [@migege](https://github.com/migege) **Created:** 5/27/2025 **Status:** ✅ Merged **Merged:** 6/3/2025 **Merged by:** [@LogicOber](https://github.com/LogicOber) **Base:** `main` ← **Head:** `main` --- ### 📝 Commits (4) - [`fbf5fdc`](https://github.com/langgenius/dify-plugins/commit/fbf5fdcb2090cc4a1833ff31738e9dedf45b916c) migege/markdown2html added - [`6dfd427`](https://github.com/langgenius/dify-plugins/commit/6dfd427819430a88da8c8491f2c4958bc0ed657a) migege/markdown2html added and README updated - [`c9a5241`](https://github.com/langgenius/dify-plugins/commit/c9a52411453e508b84d956a140ad16cf6322ecc9) Merge branch 'langgenius:main' into main - [`b1ce673`](https://github.com/langgenius/dify-plugins/commit/b1ce67325ae4b394c5e6620707d91243ad6f93e6) icon changed, i18n texts changed ### 📊 Changes **1 file changed** (+0 additions, -0 deletions) <details> <summary>View changed files</summary> ➕ `migege/markdown2html.difypkg` (+0 -0) </details> ### 📄 Description # Plugin Submission Form ## 1. Metadata <!-- Please provide the following metadata of your plugin to make it easier for the reviewer to check the changes. - Plugin Author : The author of the plugin which is defined in your manifest.yaml - Plugin Name : The name of the plugin which is defined in your manifest.yaml - Repository URL: The URL of the repository where the source code of your plugin is hosted --> - **Plugin Author**: migege - **Plugin Name**: markdown2html - **Repository URL**: https://github.com/migege/markdown2html ## 2. Submission Type - [x] New plugin submission - [ ] Version update for existing plugin ## 3. Description <!-- Please briefly describe the purpose of the new plugin or the updates made to the existing plugin --> Markdown2HTML will act as a tool node for Dify to convert Markdown text into HTML without writing to a file. ## 4. Checklist - [x] I have read and followed the Publish to Dify Marketplace guidelines - [x] I have read and comply with the Plugin Developer Agreement - [x] I confirm my plugin works properly on both Dify Community Edition and Cloud Version - [x] I confirm my plugin has been thoroughly tested for completeness and functionality - [x] My plugin brings new value to Dify ## 5. Documentation Checklist Please confirm that your plugin README includes all necessary information: - [x] Step-by-step setup instructions - [x] Detailed usage instructions - [x] All required APIs and credentials are clearly listed - [x] Connection requirements and configuration details - [x] Link to the repository for the plugin source code ## 6. Privacy Protection Information Based on Dify Plugin Privacy Protection [Guidelines](https://docs.dify.ai/plugins/publish-plugins/publish-to-dify-marketplace/plugin-privacy-protection-guidelines): ### Data Collection <!-- Does your plugin collect any user personal data? If yes, please list what types of user personal data are being collected according to the Plugin Privacy Protection Guidelines (for example: Email address, IP address, Age, etc) --> Markdown2HTML does not collect any user personal data. ### Privacy Policy - [x] I confirm that I have prepared and included a privacy policy in my plugin package based on the Plugin Privacy Protection Guidelines --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>
yindo added the pull-request label 2026-02-22 17:45:40 -05:00
yindo closed this issue 2026-02-22 17:45:47 -05:00
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 pull-request
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#1031
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?