tdsds.com/gitea
1
1
Fork 0
mirror of https://github.com/go-gitea/gitea synced 2025-12-07 13:28:25 +00:00
Code Releases Activity
17,019 Commits 19 Branches 243 Tags
b820019fec1bd955b6cb9dba1ce2f2571924ae64
Commit Graph
3 Commits
This Branch
This Branch
All Branches
Author SHA1 Message Date
Mihir JoshiandGitHub 669bbbaf24 Integration Test for Commit Search containing Square Brackets (#28751) 
Integration test for #28744 

Change keywords commit search flag from `-F` to `--fixed-strings` for
readability
 2024-01-11 11:04:45 +08:00
Mihir JoshiandGitHub 839cd26b1a Add -F to commit search to treat keywords as strings (#28744) 
Fixes #28269

The [default
behavior](https://git-scm.com/docs/git-log#Documentation/git-log.txt---basic-regexp)
of --grep in git log is to interpret the keyword as a regular
expression. This causes the search to fail in the cases where the search
keyword contains a `[`, since `[` is a special character used in grep.

If we want our keywords to be interpreted as 'strings', we should use
[-F
flag](https://git-scm.com/docs/git-log#Documentation/git-log.txt---basic-regexp).
 2024-01-10 11:28:20 +00:00
Mihir JoshiGitHubMihir
 		3d474110c1 Fix long package version names overflowing (#28619) 
Fixes #28534 

---
Before:

![image](https://github.com/go-gitea/gitea/assets/50193156/b229551c-0a7d-4a99-9553-1f11b994876a)


After:
<img width="304" alt="image"
src="https://github.com/go-gitea/gitea/assets/50193156/53d04ad0-6d5c-47e2-8a7d-30a4d5dd9959">


Should we also apply this for long filenames in Assets?
It looks like this currently:
<img width="285" alt="image"
src="https://github.com/go-gitea/gitea/assets/50193156/e2dcbb2e-30d5-4e35-b304-6274ef60bda7">

---------

Co-authored-by: Mihir <mihir.joshi@senpiper.com>
 2023-12-30 07:42:16 +00:00