feat: add task type

[GareArc]

Important

1. Make sure you have read our contribution guidelines
2. Ensure there is an associated issue and you have been assigned to it
3. Use the correct syntax to link this PR: Fixes #<issue number>.

Summary

Screenshots

Before	After
...	...

Checklist

• This change requires a documentation update, included: Dify Document
• I understand that this PR may be closed in case there was no previous discussion or issues. (This doesn't apply to typos!)
• I've added a test for each change that was introduced, and I tried as much as possible to make a single atomic change.
• I've updated the documentation accordingly.
• I ran make lint and make type-check (backend) and cd web && npx lint-staged (frontend) to appease the lint gods

[gemini-code-assist]

Summary of Changes

Hello @GareArc, I'm Gemini Code Assist¹! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request introduces a new task type for workspace synchronization operations. By adding a specific type identifier to the task payload, it enhances the clarity and manageability of tasks processed through the Redis queue, allowing for easier differentiation and potential future handling of various task categories.

Highlights

• New Task Type Constant: Introduced TASK_TYPE_SYNC_TO_WORKSPACE constant to categorize workspace synchronization tasks.
• Task Payload Enhancement: Modified the queue_credential_sync function to include the newly defined TASK_TYPE_SYNC_TO_WORKSPACE in the task payload, enabling better task identification within the Redis queue.

🧠 New Feature in Public Preview: You can now enable Memory to help Gemini Code Assist learn from your team's feedback. This makes future code reviews more consistent and personalized to your project's style. Click here to enable Memory in your admin console.

Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature	Command	Description
Code Review	/gemini review	Performs a code review for the current pull request in its current state.
Pull Request Summary	/gemini summary	Provides a summary of the current pull request in its current state.
Comment	@gemini-code-assist	Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help	/gemini help	Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

Footnotes

1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution. ↩

[gemini-code-assist]

Code Review

This pull request adds a type field to workspace synchronization tasks. The implementation is straightforward. I've suggested an improvement to use a StrEnum for the task type, which will improve maintainability and align with existing code patterns in the repository, especially as more task types may be added in the future.

[gemini-code-assist]

To improve maintainability and align with existing patterns in the codebase (e.g., ProviderType in api/models/provider.py), it would be better to define task types using a StrEnum. This makes the code more robust, especially if more task types are added in the future. You'll need to add from enum import StrEnum at the top of the file.

Suggested change

	TASK_TYPE_SYNC_TO_WORKSPACE = "sync_to_workspace"
	class TaskType(StrEnum):
	SYNC_TO_WORKSPACE = "sync_to_workspace"

[gemini-code-assist]

To go along with the TaskType enum suggestion, this should be updated to use the enum member. Since TaskType would be a StrEnum, it will correctly serialize to a string in JSON.

Suggested change

	"type": TASK_TYPE_SYNC_TO_WORKSPACE,
	"type": TaskType.SYNC_TO_WORKSPACE,

[Copilot]

Pull request overview

This PR adds a task type identifier to workspace synchronization tasks published to Redis. The change introduces a constant TASK_TYPE_SYNC_TO_WORKSPACE and includes it in the task payload to help the enterprise backend worker distinguish between different types of tasks in the queue.

Changes:

• Added TASK_TYPE_SYNC_TO_WORKSPACE constant for task type identification
• Updated task payload to include the "type" field with the new constant value

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[Copilot]

The newly added task type field is not covered by automated tests. Since this is an API contract with the enterprise backend worker that consumes these tasks, adding a test would help ensure the task structure remains consistent and prevent accidental breaking changes. Consider adding a unit test similar to the existing test in api/tests/unit_tests/services/enterprise/test_traceparent_propagation.py that verifies the task payload includes all expected fields including the new "type" field.