Mintplex-Labs/anything-llm
1
0
Fork 0
mirror of https://github.com/Mintplex-Labs/anything-llm.git synced 2026-07-19 14:13:35 -04:00
Code Issues 328 Packages Projects Releases 10 Wiki Activity

[GH-ISSUE #557] Pull Request Template for better Development #326

New Issue
Closed
opened 2026-02-22 18:18:58 -05:00 by yindo · 1 comment
yindo commented 2026-02-22 18:18:58 -05:00
Owner
Copy Link
Copy Source

Originally created by @imjaglan on GitHub (Jan 9, 2024).
Original GitHub issue: https://github.com/Mintplex-Labs/anything-llm/issues/557

Originally assigned to: @timothycarambat on GitHub.

We should implement a PR template for getting a good understanding of the issue solved along with the extra description so that, whoever is going to review the pr can easily review it , Every time someone will make a pr he will see this PR description automatically.

If you Agree @timothycarambat , I volunteer to make a PR for this??

I am thinking of something like this:

💻 Change Type

  • ✨ feat
  • 🐛 fix
  • ♻️ refactor
  • 💄 style
  • 🔨 chore
  • 📝 docs

Description of Change

  • Here we can write the description of the change, or a Loom video explaining the code.

Additional Information

  • Add any other context about the Pull Request here.
Originally created by @imjaglan on GitHub (Jan 9, 2024). Original GitHub issue: https://github.com/Mintplex-Labs/anything-llm/issues/557 Originally assigned to: @timothycarambat on GitHub. We should implement a PR template for getting a good understanding of the issue solved along with the extra description so that, whoever is going to review the pr can easily review it , Every time someone will make a pr he will see this PR description automatically. If you Agree @timothycarambat , I volunteer to make a PR for this?? ## I am thinking of something like this: ### 💻 Change Type <!-- For change type, change [ ] to [x]. --> - [ ] ✨ feat - [ ] 🐛 fix - [ ] ♻️ refactor - [ ] 💄 style - [ ] 🔨 chore - [ ] 📝 docs ### Description of Change - Here we can write the description of the change, or a Loom video explaining the code. ### Additional Information - Add any other context about the Pull Request here.
yindo added the documentationcore-team-only labels 2026-02-22 18:18:58 -05:00
yindo closed this issue 2026-02-22 18:18:58 -05:00
yindo commented 2026-02-22 18:18:58 -05:00
Author
Owner
Copy Link
Copy Source

@timothycarambat commented on GitHub (Jan 9, 2024):

Absolutely do need to do this. It's actually on our internal Asana board. Let the core-team handle this because there are some specific things that need to be added to this flow for Bugs/Features etc etc and other QoL items!

Thank you for making the issue because it's reminded me to do it!

@timothycarambat commented on GitHub (Jan 9, 2024): Absolutely do need to do this. It's actually on our internal Asana board. Let the core-team handle this because there are some specific things that need to be added to this flow for Bugs/Features etc etc and other QoL items! Thank you for making the issue because it's reminded me to do it!
yindo changed title from Pull Request Template for better Development to [GH-ISSUE #557] Pull Request Template for better Development 2026-06-05 14:34:43 -04:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
Desktop
Docker
Integration Request
Integration Request
OS: Linux
OS: Mobile
OS: Windows
UI/UX
blocked
bug
bug
core-team-only
documentation
duplicate
embed-widget
enhancement
feature request
github_actions
good first issue
investigating
needs info / can't replicate
possible bug
pull-request
Mirrored from GitHub Pull Request
 question
stage: specifications
wontfix
No Label core-team-only documentation
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: Mintplex-Labs/anything-llm#326
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?