-
-
Notifications
You must be signed in to change notification settings - Fork 5.6k
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
Make WIP prefixes case insensitive, e.g. allow Draft
as a WIP prefix
#19780
Conversation
The issue was that only the actual title was converted to uppercase, but not the prefix as specified in `WORK_IN_PROGRESS_PREFIXES`. As a result, the following did not work: WORK_IN_PROGRESS_PREFIXES=Draft:,[Draft],WIP:,[WIP] One possible workaround was: WORK_IN_PROGRESS_PREFIXES=DRAFT:,[DRAFT],WIP:,[WIP] Then indeed one could use `Draft` (as well as `DRAFT`) in the title. However, the link `Start the title with DRAFT: to prevent the pull request from being merged accidentally.` showed the suggestion in uppercase; so it is not possible to show it as `Draft`. This PR fixes it, and allows to use `Draft` in `WORK_IN_PROGRESS_PREFIXES`. Fixes go-gitea#19779.
Codecov Report
@@ Coverage Diff @@
## main #19780 +/- ##
=======================================
Coverage ? 47.28%
=======================================
Files ? 957
Lines ? 133339
Branches ? 0
=======================================
Hits ? 63053
Misses ? 62617
Partials ? 7669
Continue to review full report at Codecov.
|
You also need to fix GetWorkInProgressPrefix() a few lines below that. |
In actuality I think the better solution would be to go to modules/setting/repository.go line 297 and uppercase the WorkInProgressPrefixes just after reading them from the configuration file. Oh I see these are suggested to the User as potential prefixes in which case permanently uppercasing them is not ideal. |
It's better to update the comment or document that is not case sensitive. |
I think that would be equivalent to the workaround I mentioned:
Excellent point, fixed in 11754a1. This is needed so that the "Remove Draft Prefix" button works. I tested it and it seems to work. |
Cool. Thanks... It would be helpful to update: gitea/custom/conf/app.example.ini Line 941 in 4266bd9
and
To mention that these are matched in a case insensitive manner too. Then I will approve and we can get this merged. |
@zeripath I made the changes, good point. Let me know if there is anything else to be done. |
Draft
working as a WIP prefixDraft
as a WIP prefix
make lgtm work |
I think it would be appropriate to backport this to 1.16. If you would like to do this: In your git repo ## Update your repo
git pull --all
## Checkout a backport branch
git checkout origin/release/v1.16 -b backport-19780-v1.16
## Cherry pick the above commit
git cherry-pick 8720f87
## and fix any conflicts...
## Adjust the commit message to make the first line after the title (and its blank line):
## Backport #19780
git commit --amend
## Push it up
git push certik backport-19780-v1.16
## Then open a PR
xdg-open https://github.com/go-gitea/gitea/compare/release/v1.16...certik:backport-19780-v1.16
## Put it on the v1.16.9 milestone with the label: kind/bug
## And then one of us will add the backport/done label to this. |
* giteaofficial/main: Make WIP prefixes case insensitive, e.g. allow `Draft` as a WIP prefix (go-gitea#19780) Fix follower display on user page (go-gitea#19805) Show source/target branches on PR's list (go-gitea#19747)
go-gitea#19780) Backport go-gitea#19780 The issue was that only the actual title was converted to uppercase, but not the prefix as specified in `WORK_IN_PROGRESS_PREFIXES`. As a result, the following did not work: WORK_IN_PROGRESS_PREFIXES=Draft:,[Draft],WIP:,[WIP] One possible workaround was: WORK_IN_PROGRESS_PREFIXES=DRAFT:,[DRAFT],WIP:,[WIP] Then indeed one could use `Draft` (as well as `DRAFT`) in the title. However, the link `Start the title with DRAFT: to prevent the pull request from being merged accidentally.` showed the suggestion in uppercase; so it is not possible to show it as `Draft`. This PR fixes it, and allows to use `Draft` in `WORK_IN_PROGRESS_PREFIXES`. Fixes go-gitea#19779. Co-authored-by: zeripath <art27@cantab.net>
#19780) (#19811) Backport #19780 The issue was that only the actual title was converted to uppercase, but not the prefix as specified in `WORK_IN_PROGRESS_PREFIXES`. As a result, the following did not work: WORK_IN_PROGRESS_PREFIXES=Draft:,[Draft],WIP:,[WIP] One possible workaround was: WORK_IN_PROGRESS_PREFIXES=DRAFT:,[DRAFT],WIP:,[WIP] Then indeed one could use `Draft` (as well as `DRAFT`) in the title. However, the link `Start the title with DRAFT: to prevent the pull request from being merged accidentally.` showed the suggestion in uppercase; so it is not possible to show it as `Draft`. This PR fixes it, and allows to use `Draft` in `WORK_IN_PROGRESS_PREFIXES`. Fixes #19779. Co-authored-by: zeripath <art27@cantab.net>
## [1.16.9](https://github.com/go-gitea/gitea/releases/tag/1.16.9) - 2022-06-20 * BUGFIXES * Fix permission check for delete tag (go-gitea#19985) (go-gitea#20001) * Only log non ErrNotExist errors in git.GetNote (go-gitea#19884) (go-gitea#19905) * Use exact search instead of fuzzy search for branch filter dropdown (go-gitea#19885) (go-gitea#19893) * Set Setpgid on child git processes (go-gitea#19865) (go-gitea#19881) * Import git from alpine 3.16 repository as 2.30.4 is needed for `safe.directory = '*'` to work but alpine 3.13 has 2.30.3 (go-gitea#19876) * Ensure responses are context.ResponseWriters (go-gitea#19843) (go-gitea#19859) * Fix count bug (go-gitea#19850) * Fix raw endpoint PDF file headers (go-gitea#19825) (go-gitea#19826) * Make WIP prefixes case insensitive, e.g. allow `Draft` as a WIP prefix (go-gitea#19780) (go-gitea#19811) * Fix NotificationUnreadCount (go-gitea#19802) * Prevent NPE when cache service is disabled (go-gitea#19703) (go-gitea#19783) * Detect truncated utf-8 characters at the end of content as still representing utf-8 (go-gitea#19773) (go-gitea#19774) * Fix doctor pq: syntax error at or near "." quote user table name (go-gitea#19765) (go-gitea#19770) * Fix bug (go-gitea#19757) Signed-off-by: Andrew Thornton <art27@cantab.net>
go-gitea#19780) The issue was that only the actual title was converted to uppercase, but not the prefix as specified in `WORK_IN_PROGRESS_PREFIXES`. As a result, the following did not work: WORK_IN_PROGRESS_PREFIXES=Draft:,[Draft],WIP:,[WIP] One possible workaround was: WORK_IN_PROGRESS_PREFIXES=DRAFT:,[DRAFT],WIP:,[WIP] Then indeed one could use `Draft` (as well as `DRAFT`) in the title. However, the link `Start the title with DRAFT: to prevent the pull request from being merged accidentally.` showed the suggestion in uppercase; so it is not possible to show it as `Draft`. This PR fixes it, and allows to use `Draft` in `WORK_IN_PROGRESS_PREFIXES`. Fixes go-gitea#19779. Co-authored-by: zeripath <art27@cantab.net>
There is a bug in WIP prefix matching which results in only all uppercase prefixes being matched.
The issue was that only the actual title was converted to uppercase, but
not the prefix as specified in
WORK_IN_PROGRESS_PREFIXES
. As a result,the following did not work:
One possible workaround was:
Then indeed one could use
Draft
(as well asDRAFT
) in the title.However, the link
Start the title with DRAFT: to prevent the pull request from being merged accidentally.
showed the suggestion in uppercase; soit is not possible to show it as
Draft
. This PR fixes it, and allowsto use
Draft
inWORK_IN_PROGRESS_PREFIXES
.Fixes #19779.