langgenius/dify
1
0
Fork 0
mirror of https://github.com/langgenius/dify.git synced 2026-07-21 20:15:31 -04:00
Code Issues 775 Packages Projects Releases 10 Wiki Activity

[PR #23847] chore: rename misleading 'chore.yaml' issue template to 'refactor.yml' #30419

New Issue
Closed
opened 2026-02-21 20:47:27 -05:00 by yindo · 0 comments
yindo commented 2026-02-21 20:47:27 -05:00
Owner
Copy Link
Copy Source

Original Pull Request: https://github.com/langgenius/dify/pull/23847

State: closed
Merged: Yes

Summary

This PR renames the misleading chore.yaml issue template to refactor.yml to better reflect its actual purpose.

Fixes #23846

Problem

The current issue template file chore.yaml has a misleading name that doesn't clearly indicate its purpose. The template is actually for refactoring tasks, not general chores.

Changes

  • Renamed .github/ISSUE_TEMPLATE/chore.yaml to .github/ISSUE_TEMPLATE/refactor.yml

Why this change?

  1. The template title is "✨ Refactor"
  2. It applies the "refactor" label
  3. All fields in the template focus on refactoring motivation and context
  4. The new name matches the template's actual purpose
  5. Uses .yml extension for consistency with other templates

Screenshots

Before After
chore.yaml refactor.yml

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 dev/reformat(backend) and cd web && npx lint-staged(frontend) to appease the lint gods
**Original Pull Request:** https://github.com/langgenius/dify/pull/23847 **State:** closed **Merged:** Yes --- ## Summary This PR renames the misleading `chore.yaml` issue template to `refactor.yml` to better reflect its actual purpose. Fixes #23846 ## Problem The current issue template file `chore.yaml` has a misleading name that doesn't clearly indicate its purpose. The template is actually for **refactoring** tasks, not general chores. ## Changes - Renamed `.github/ISSUE_TEMPLATE/chore.yaml` to `.github/ISSUE_TEMPLATE/refactor.yml` ## Why this change? 1. The template title is "✨ Refactor" 2. It applies the "refactor" label 3. All fields in the template focus on refactoring motivation and context 4. The new name matches the template's actual purpose 5. Uses `.yml` extension for consistency with other templates ## Screenshots | Before | After | |--------|-------| | `chore.yaml` | `refactor.yml` | ## Checklist - [ ] This change requires a documentation update, included: [Dify Document](https://github.com/langgenius/dify-docs) - [x] I understand that this PR may be closed in case there was no previous discussion or issues. (This doesn't apply to typos\!) - [x] I've added a test for each change that was introduced, and I tried as much as possible to make a single atomic change. - [x] I've updated the documentation accordingly. - [x] I ran `dev/reformat`(backend) and `cd web && npx lint-staged`(frontend) to appease the lint gods
yindo added the pull-request label 2026-02-21 20:47:27 -05:00
yindo closed this issue 2026-02-21 20:47:27 -05:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
Knowledge Pipeline
Proposal
WIP
cloud
dependencies
feat:webapp
good first issue
outdated
performance
pull-request
Mirrored from GitHub Pull Request
 python:uv
refactor
size:L
stale
status: accepting prs
status: blocked
status: in discussion
stt & tts
vulnerablity
web
wont-fix
🌊 feat:workflow
🌚 invalid
🐞 bug
👻 feat:rag
💪 enhancement
📚 documentation
🔨 feat:tools
🙋‍♂️ question
🙏 help wanted
🤔 cant-reproduce
🤖 feat:agent
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#30419
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?