-
-
Notifications
You must be signed in to change notification settings - Fork 9.4k
Pull requests: halo-dev/halo
Author
Label
Projects
Milestones
Reviews
Assignee
Sort
Pull requests list
feat: add dynamic list input
area/ui
Issues or PRs related to the Halo UI
kind/feature
Categorizes issue or PR as related to a new feature.
release-note
Denotes a PR that will be considered when it comes time to generate release notes.
refactor: add list options for sync all synchronizer
area/core
Issues or PRs related to the Halo Core
kind/improvement
Categorizes issue or PR as related to a improvement.
release-note-none
Denotes a PR that doesn't merit a release note.
WIP: feat: add batch setting for partial post fields
area/ui
Issues or PRs related to the Halo UI
do-not-merge/work-in-progress
Indicates that a PR should not merge because it is a work in progress.
kind/feature
Categorizes issue or PR as related to a new feature.
release-note
Denotes a PR that will be considered when it comes time to generate release notes.
refactor: enhance cache management in plugin setting config
area/core
Issues or PRs related to the Halo Core
area/plugin
Issues or PRs related to the Plugin Provider
kind/feature
Categorizes issue or PR as related to a new feature.
release-note
Denotes a PR that will be considered when it comes time to generate release notes.
WIP: feat: add secret select input
area/ui
Issues or PRs related to the Halo UI
do-not-merge/work-in-progress
Indicates that a PR should not merge because it is a work in progress.
kind/feature
Categorizes issue or PR as related to a new feature.
release-note
Denotes a PR that will be considered when it comes time to generate release notes.
refactor: remove phone field for user form
area/ui
Issues or PRs related to the Halo UI
kind/improvement
Categorizes issue or PR as related to a improvement.
release-note-none
Denotes a PR that doesn't merit a release note.
refactor: hide move group button when no attachment groups are present
area/ui
Issues or PRs related to the Halo UI
kind/improvement
Categorizes issue or PR as related to a improvement.
release-note-none
Denotes a PR that doesn't merit a release note.
WIP: feat: add management and view pages for extension points
area/ui
Issues or PRs related to the Halo UI
do-not-merge/work-in-progress
Indicates that a PR should not merge because it is a work in progress.
kind/feature
Categorizes issue or PR as related to a new feature.
release-note
Denotes a PR that will be considered when it comes time to generate release notes.
feat: add method to find path of a specified node in a category tree
area/core
Issues or PRs related to the Halo Core
do-not-merge/work-in-progress
Indicates that a PR should not merge because it is a work in progress.
kind/feature
Categorizes issue or PR as related to a new feature.
release-note
Denotes a PR that will be considered when it comes time to generate release notes.
feat: implement persistent token based remember me mechanism
area/core
Issues or PRs related to the Halo Core
kind/feature
Categorizes issue or PR as related to a new feature.
release-note
Denotes a PR that will be considered when it comes time to generate release notes.
refactor: preserve post title when opening settings
approved
Indicates a PR has been approved by an approver from all required OWNERS files.
area/ui
Issues or PRs related to the Halo UI
kind/improvement
Categorizes issue or PR as related to a improvement.
release-note
Denotes a PR that will be considered when it comes time to generate release notes.
feat: range selection feature to default editor
area/editor
Issues or PRs related to the Editor
kind/feature
Categorizes issue or PR as related to a new feature.
release-note
Denotes a PR that will be considered when it comes time to generate release notes.
feat: support hide categories and posts from the list
area/core
Issues or PRs related to the Halo Core
do-not-merge/work-in-progress
Indicates that a PR should not merge because it is a work in progress.
kind/feature
Categorizes issue or PR as related to a new feature.
release-note
Denotes a PR that will be considered when it comes time to generate release notes.
refactor: remove page cache feature
area/core
Issues or PRs related to the Halo Core
do-not-merge/work-in-progress
Indicates that a PR should not merge because it is a work in progress.
kind/api-change
Categorizes issue or PR as related to adding, removing, or otherwise changing an API
needs-rebase
Indicates a PR cannot be merged because it has merge conflicts with HEAD.
release-note
Denotes a PR that will be considered when it comes time to generate release notes.
feat: add gap cursor for top-level block nodes in default editor
area/editor
Issues or PRs related to the Editor
kind/feature
Categorizes issue or PR as related to a new feature.
needs-rebase
Indicates a PR cannot be merged because it has merge conflicts with HEAD.
release-note
Denotes a PR that will be considered when it comes time to generate release notes.
feat: add device management mechanism
area/core
Issues or PRs related to the Halo Core
kind/feature
Categorizes issue or PR as related to a new feature.
release-note
Denotes a PR that will be considered when it comes time to generate release notes.
fix: the e2e script exit code handling is incorrect
do-not-merge/work-in-progress
Indicates that a PR should not merge because it is a work in progress.
kind/bug
Categorizes issue or PR as related to a bug.
release-note-none
Denotes a PR that doesn't merit a release note.
#6097
opened Jun 18, 2024 by
LinuxSuRen
•
Draft
WIP: Refactor search engine extension
area/core
Issues or PRs related to the Halo Core
do-not-merge/work-in-progress
Indicates that a PR should not merge because it is a work in progress.
kind/api-change
Categorizes issue or PR as related to adding, removing, or otherwise changing an API
kind/improvement
Categorizes issue or PR as related to a improvement.
needs-rebase
Indicates a PR cannot be merged because it has merge conflicts with HEAD.
release-note-none
Denotes a PR that doesn't merit a release note.
#6082
opened Jun 14, 2024 by
JohnNiang
Loading…
ProTip!
Follow long discussions with comments:>50.