mirror of
https://github.com/BookStackApp/BookStack.git
synced 2026-02-05 00:29:48 +03:00
Search Term Log #807
Reference in New Issue
Block a user
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?
Originally created by @nvnvnvnvn on GitHub (Sep 7, 2018).
Describe the feature you'd like
View a log/list of search terms users have entered.
Describe the benefits this feature would bring to BookStack users
Will help to know what they are looking for and work to make our results return better matches for it.
Additional context
Could be last 100 searches (would be nice to know if it was a global search, a search within a book, etc). Could be a log file we can access, or would be nice to be able to view from the settings page or such.
@nvnvnvnvn commented on GitHub (Dec 28, 2018):
@ssddanbrown
I'm sure it must be difficult / impossible to keep up with all posts. How do you determine which ones to work on / implement, and is there a way to know when to expect the ones you are working on?
My boss asks for status of things and I just have to say I don't know.
It is probably my lack of understanding how Github works.
@ssddanbrown commented on GitHub (Dec 28, 2018):
Hi @nvnvnvnvn,
There's not too much of an official process. I try to keep things relaxed so that the project doesn't feel like 'work' so that I can do what I want to ensure I enjoy working on BookStack.
Generally, I have an idea of large-scale features I want to implement. Usually each release is focused on one of these and then other bits get assigned. For each release I'll create a GitHub milestone which issues are assigned to and then that milestone will be worked through until release, then the cycle repeats. Here's the milestone for the next release. Every so often I'll sort issues by number of 👍's to see what people generally want the most.
For any big features I work on I'll usually open up a pull request so I can somewhat document the implement the idea and so feedback can be provided. Here's the next thing I'm working on for example.
Often in the release blog posts I'll give an indication as to what I'm looking to focus on next at the bottom of the post in a "Next Steps" section but that's not always reliable.