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 #678] [MERGED] update: commit easydoc dify plugin(v0.0.1) #1096

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

📋 Pull Request Information

Original PR: https://github.com/langgenius/dify-plugins/pull/678
Author: @sycamore792
Created: 6/12/2025
Status: ✅ Merged
Merged: 6/16/2025
Merged by: @LogicOber

Base: main ← Head: main

📝 Commits (2)

  • aab06ef update: commit easydoc dify plugin(v0.0.1)
  • 1a6832e update: Update EasyDoc plugin information: modify privacy policy link, update author info, add GitHub link, enhance API key validation, improve error handling, and remove unnecessary print statements.

📊 Changes

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

View changed files

➕ easylink-ai/easydoc-plugin/easydoc-dify-plugin.difypkg (+0 -0)

📄 Description

Plugin Submission Form

1. Metadata

  • Plugin Author:
  • Plugin Name:
  • Repository URL:

2. Submission Type

  • [✅] New plugin submission
  • Version update for existing plugin

3. Description

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

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/678 **Author:** [@sycamore792](https://github.com/sycamore792) **Created:** 6/12/2025 **Status:** ✅ Merged **Merged:** 6/16/2025 **Merged by:** [@LogicOber](https://github.com/LogicOber) **Base:** `main` ← **Head:** `main` --- ### 📝 Commits (2) - [`aab06ef`](https://github.com/langgenius/dify-plugins/commit/aab06efb07b5916e3ec7f05187c05b4867851ccf) update: commit easydoc dify plugin(v0.0.1) - [`1a6832e`](https://github.com/langgenius/dify-plugins/commit/1a6832e0bebdd15d647dbe983ab506dd64a29b90) update: Update EasyDoc plugin information: modify privacy policy link, update author info, add GitHub link, enhance API key validation, improve error handling, and remove unnecessary print statements. ### 📊 Changes **1 file changed** (+0 additions, -0 deletions) <details> <summary>View changed files</summary> ➕ `easylink-ai/easydoc-plugin/easydoc-dify-plugin.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**: - **Plugin Name**: - **Repository URL**: ## 2. Submission Type - [✅] 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 --> ## 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](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) --> ### Privacy Policy - [✅] 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:47:58 -05:00
yindo closed this issue 2026-02-22 17:48:00 -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#1096
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?