Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

full-text search doesn't work in fields with branches while editing pull request #14689

Closed
1 of 6 tasks
lakostin opened this issue Feb 15, 2021 · 0 comments · Fixed by #14694
Closed
1 of 6 tasks

full-text search doesn't work in fields with branches while editing pull request #14689

lakostin opened this issue Feb 15, 2021 · 0 comments · Fixed by #14694
Labels
type/proposal The new feature has not been accepted yet but needs to be discussed first.

Comments

@lakostin
Copy link

  • Gitea version (or commit ref):
    1.14.0+dev-534-gedbc5c86d
  • Git version:
    2.26.2
  • Operating system:
    docker Alpine Linux v3.12
  • Database (use [x]):
    • PostgreSQL
    • MySQL
    • MSSQL
    • SQLite
  • Can you reproduce the bug at https://try.gitea.io:
    • Yes (provide example URL)
    • No
  • Log gist:

Description

If i want to change target or source branch in already created pull request, i have to write the name of new branch starting from organization. If i type just branch name it won't be found.
...

Screenshots

Screenshot from 2021-02-15 18-15-13
Screenshot from 2021-02-15 18-14-55

@lunny lunny added the type/proposal The new feature has not been accepted yet but needs to be discussed first. label Feb 15, 2021
zeripath added a commit to zeripath/gitea that referenced this issue Feb 15, 2021
This PR adds `fullTextSearch: 'exact'` to most dropdown
invocations meaning that if there is a search box for the
dropdown it will automatically do a fullTextSearch looking
for the provided fragment instead of starting at the beginning

We should consider changing other places that use
`fullTextSearch: true` to `'exact'` because these will be using a
fuzzy-textual search that doesn't necessarily return the
expected results.

Fix go-gitea#14689

Signed-off-by: Andrew Thornton <[email protected]>
lunny pushed a commit that referenced this issue Feb 16, 2021
This PR adds `fullTextSearch: 'exact'` to most dropdown
invocations meaning that if there is a search box for the
dropdown it will automatically do a fullTextSearch looking
for the provided fragment instead of starting at the beginning

We should consider changing other places that use
`fullTextSearch: true` to `'exact'` because these will be using a
fuzzy-textual search that doesn't necessarily return the
expected results.

Fix #14689

Signed-off-by: Andrew Thornton <[email protected]>
@go-gitea go-gitea locked and limited conversation to collaborators May 13, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
type/proposal The new feature has not been accepted yet but needs to be discussed first.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants