aboutsummaryrefslogtreecommitdiffstats
path: root/options
Commit message (Collapse)AuthorAgeFilesLines
* [skip ci] Updated translations via CrowdinGiteaBot2024-01-241-1/+83
|
* Add missing exclusive in advanced label options (#28322)Luca Zulberti2024-01-221-3/+3
| | | | | | | | Hi, I think these changes could be useful for default labels when creating new repos. The PR includes the following changes: - Add missing exclusive flag for Kind/ scope in labels. - Move Breaking label into new Compat/ scope.
* [skip ci] Updated licenses and gitignoresGiteaBot2024-01-225-0/+265
|
* Don't show new pr button when page is not compare pull (#26431)yp053272024-01-211-0/+1
| | | | | | | | | | | | | | | | | | | | | Before: ![image](https://github.com/go-gitea/gitea/assets/18380374/ba69252f-3582-414a-9d62-b2b78d7035dd) After: ![image](https://github.com/go-gitea/gitea/assets/18380374/71b8587c-b96e-48fb-b3e5-1a2a8b5d06fa) (TestOrg:test is a tag not branch) Problem: In the template, we will not add `compare pull` class when `PageIsComparePull` is false. https://github.com/go-gitea/gitea/blob/a370efc13f0e1ea309e324639832832bc14cb6dc/templates/repo/diff/compare.tmpl#L2 But in the js, we are using `.repository.compare.pull` to find the button: https://github.com/go-gitea/gitea/blob/a370efc13f0e1ea309e324639832832bc14cb6dc/web_src/js/features/repo-legacy.js#L552-L563 So, if `PageIsComparePull` is false, the `New Pull Request` button will be there, but has no response when we click it.
* Add support for sha256 repositories (#23894)Adam Majer2024-01-191-0/+3
| | | | | | | | | | | | | | | | Currently only SHA1 repositories are supported by Gitea. This adds support for alternate SHA256 with the additional aim of easier support for additional hash types in the future. Fixes: #13794 Limited by: https://github.com/go-git/go-git/issues/899 Depend on: #28138 <img width="776" alt="图片" src="https://github.com/go-gitea/gitea/assets/81045/5448c9a7-608e-4341-a149-5dd0069c9447"> --------- Co-authored-by: Lunny Xiao <xiaolunwen@gmail.com> Co-authored-by: 6543 <6543@obermui.de>
* Fix some RPM registry flaws (#28782)KN4CK3R2024-01-191-0/+3
| | | | | | | | | | | | | | | | | | | Related #26984 (https://github.com/go-gitea/gitea/pull/26984#issuecomment-1889588912) Fix admin cleanup message. Fix models `Get` not respecting default values. Rebuild RPM repository files after cleanup. Do not add RPM group to package version name. Force stable sorting of Alpine/Debian/RPM repository data. Fix missing deferred `Close`. Add tests for multiple RPM groups. Removed non-cached `ReplaceAllStringRegex`. If there are multiple groups available, it's stated in the package installation screen: ![grafik](https://github.com/go-gitea/gitea/assets/1666336/8f132760-882c-4ab8-9678-77e47dfc4415)
* Fix display latest sync time for pull mirrors on the repo page (#28841)yp053272024-01-181-0/+1
| | | | | | | | | | | | | | Follow #28712 1. Missing Locale word `mirror_sync` 2. Maybe forgot checking the conflict from #27760 Before: ![image](https://github.com/go-gitea/gitea/assets/18380374/6100d35b-7fe3-4095-9c24-7875568f7380) After: ![image](https://github.com/go-gitea/gitea/assets/18380374/69647169-b812-45bc-a267-ab28f2df6ef6)
* Add branch protection setting for ignoring stale approvals (#28498)Jimmy Praet2024-01-151-0/+2
| | | | | | | | | | | | | | | | | | | | | | Fixes #27114. * In Gitea 1.12 (#9532), a "dismiss stale approvals" branch protection setting was introduced, for ignoring stale reviews when verifying the approval count of a pull request. * In Gitea 1.14 (#12674), the "dismiss review" feature was added. * This caused confusion with users (#25858), as "dismiss" now means 2 different things. * In Gitea 1.20 (#25882), the behavior of the "dismiss stale approvals" branch protection was modified to actually dismiss the stale review. For some users this new behavior of dismissing the stale reviews is not desirable. So this PR reintroduces the old behavior as a new "ignore stale approvals" branch protection setting. --------- Co-authored-by: delvh <dev.lh@web.de>
* Forbid removing the last admin user (#28337)yp053272024-01-151-0/+3
| | | Co-authored-by: Lunny Xiao <xiaolunwen@gmail.com>
* Recommend/convert to use case-sensitive collation for MySQL/MSSQL (#28662)wxiaoguang2024-01-101-0/+8
| | | | | | | | | | | | | | | | | | Mainly for MySQL/MSSQL. It is important for Gitea to use case-sensitive database charset collation. If the database is using a case-insensitive collation, Gitea will show startup error/warning messages, and show the errors/warnings on the admin panel's Self-Check page. Make `gitea doctor convert` work for MySQL to convert the collations of database & tables & columns. * Fix #28131 ## :warning: BREAKING :warning: It is not quite breaking, but it's highly recommended to convert the database&table&column to a consistent and case-sensitive collation.
* [skip ci] Updated licenses and gitignoresGiteaBot2024-01-087-4/+263
|
* [skip ci] Updated translations via CrowdinGiteaBot2024-01-072-0/+14
|
* Fix grammar in `actions.variables.id_not_exist` (en-US) (#28680)wackbyte2024-01-031-1/+1
| | | Fixes the capitalization and grammar of the key.
* Fix grammar issues on the repository Actions page (en-US) (#28679)wackbyte2024-01-031-2/+2
| | | | Fixes a few grammar issues in the en-US localization of the repository Actions page.
* [skip ci] Updated translations via CrowdinGiteaBot2024-01-011-13/+13
|
* [skip ci] Updated translations via CrowdinGiteaBot2023-12-291-1/+1
|
* [skip ci] Updated translations via CrowdinGiteaBot2023-12-281-4/+5
|
* [skip ci] Updated translations via CrowdinGiteaBot2023-12-272-1/+49
|
* [skip ci] Updated translations via CrowdinGiteaBot2023-12-2625-45/+8
|
* [skip ci] Updated licenses and gitignoresGiteaBot2023-12-252-0/+15
|
* [skip ci] Updated translations via CrowdinGiteaBot2023-12-201-0/+4
|
* Only check online runner when detecting matching runners in workflows (#28286)yp053272023-12-181-1/+1
| | | | | | | | | | | Mentioned: [#28277](https://github.com/go-gitea/gitea/issues/28277#issuecomment-1831325276) We should only check online runner when detecting matching runners in workflows, as if runner is not online, the workflow will not run. ![image](https://github.com/go-gitea/gitea/assets/18380374/11855e9d-7241-4b7a-b8d7-49dbb94ba1c5)
* [skip ci] Updated translations via CrowdinGiteaBot2023-12-181-2/+2
|
* Remove duplicate option in admin screen and now-unused translation keys (#28492)The Magician2023-12-171-1/+0
| | | | | | | | | | | | | Resolves https://github.com/go-gitea/gitea/issues/28451. This change follows the recommendation by wxiaoguang to remove the "Disable Minimum Key Size Check" from the "Service Configuration" section of the UI, because this option belongs to the "SSH Configuration" section of the administration menu and already has a functioning indicator in that section of the UI. --------- Co-authored-by: wxiaoguang <wxiaoguang@gmail.com>
* [skip ci] Updated translations via CrowdinGiteaBot2023-12-171-7/+24
|
* [skip ci] Updated translations via CrowdinGiteaBot2023-12-131-0/+3
|
* [skip ci] Updated translations via CrowdinGiteaBot2023-12-1227-319/+87
|
* [skip ci] Updated licenses and gitignoresGiteaBot2023-12-111-0/+15
|
* [skip ci] Updated translations via CrowdinGiteaBot2023-12-092-36/+43
|
* Improve text in Security settings (#28393)Panagiotis "Ivory" Vasilopoulos2023-12-081-7/+10
| | | | | | | | - en-US: Rename "Scratch Tokens" to "single-use recovery keys". Longer, but clearer. - Improve titles - TOTP: Improve description - TOTP: Inform user about Scratch Tokens to encourage TOTP usage - WebAuthn: Add loss of access warning
* [skip ci] Updated translations via CrowdinGiteaBot2023-12-071-1/+1
|
* [skip ci] Updated translations via CrowdinGiteaBot2023-12-061-1/+1
|
* [skip ci] Updated licenses and gitignoresGiteaBot2023-12-042-0/+47
|
* Fix wrong link in `protect_branch_name_pattern_desc` (#28313)yp053272023-12-011-1/+1
| | | | The current href will link to `https://domain/owner/repo/settings/branches/github.com/gobwas/glob`
* Add guide page to actions when there's no workflows (#28145)yp053272023-11-211-0/+3
| | | | | | | | | Before: ![image](https://github.com/go-gitea/gitea/assets/18380374/599d40c1-9b8d-4189-9286-c9c36fb780dd) After: ![image](https://github.com/go-gitea/gitea/assets/18380374/848a73d1-aaec-478f-93a7-adcc7ee18907)
* Fix empty action run title (#28113)Lunny Xiao2023-11-211-0/+1
| | | Fix #27901
* Fix typo in `packages.cleanup.success` (#28133)Jason Song2023-11-201-1/+1
| | | | Follow https://github.com/go-gitea/gitea/pull/28129#discussion_r1398971596
* Add missing `packages.cleanup.success` (#28129)Jason Song2023-11-201-0/+1
| | | | | | | Used at https://github.com/go-gitea/gitea/blob/a3348bfc4d565328f3608b1ee555f61be9fce1c3/routers/web/admin/packages.go#L111 <img width="1325" alt="image" src="https://github.com/go-gitea/gitea/assets/9418365/60edc1fa-eea8-4d74-a7ec-96bd5461a53f">
* [skip ci] Updated translations via CrowdinGiteaBot2023-11-201-18/+18
|
* [skip ci] Updated translations via CrowdinGiteaBot2023-11-141-29/+62
|
* [skip ci] Updated licenses and gitignoresGiteaBot2023-11-138-0/+341
|
* [skip ci] Updated translations via CrowdinGiteaBot2023-11-031-0/+4
|
* Add `Hide/Show all checks` button to commit status check (#26284)yp053272023-11-021-0/+2
| | | | | | | | | | | | | | | | | | | | | | | | | Step one for a GitHub like commit status check ui: ![image](https://github.com/go-gitea/gitea/assets/18380374/22953b88-1f91-4d19-bc57-ad92d33fa11f) ![image](https://github.com/go-gitea/gitea/assets/18380374/78572a49-c9b0-472b-86a8-8293197e807b) ![image](https://github.com/go-gitea/gitea/assets/18380374/bc5c8d1c-2ab5-4b03-b8c6-20c34b86d856) Step two: ![image](https://github.com/go-gitea/gitea/assets/18380374/938b359e-8823-4192-b82d-55fa40b986fd) ![image](https://github.com/go-gitea/gitea/assets/18380374/2de5bb8f-40f5-462a-8d6d-bac13a32bc2a) The design now will list all commit status checks which takes too much space. This is a pre-improve for #26247 --------- Co-authored-by: delvh <dev.lh@web.de> Co-authored-by: silverwind <me@silverwind.io> Co-authored-by: wxiaoguang <wxiaoguang@gmail.com>
* [skip ci] Updated translations via CrowdinGiteaBot2023-10-281-11/+11
|
* [skip ci] Updated translations via CrowdinGiteaBot2023-10-2713-4/+182
|
* Package repository/documentation link unification (#27804)Danila Fominykh2023-10-2714-56/+0
| | | | | | | | | Some translations are duplicated for the same package fields; it should be possible to use the same approach. Checked packages to use the same forms in templates. 1. Removed repeated translations for the same fields 2. Linked template files to the same translation fields 3. Added repository site link for nuget packages
* Fix typo when updating email address (#27789)Joel Wetzell2023-10-251-1/+1
| | | - correct text that is shown when attempting to change an email address
* Improve pull request command line instructions (#27778)Brecht Van Lommel2023-10-251-6/+5
| | | | | | | | | | | | | * Show checkout instructions also when there is no permission to push, for anyone who wants to locally test the changes. * First checkout the branch exactly as is, without immediately having to solve merge conflicts. Leave this to the merge step, since it's often convenient to test a change without worrying about this. * Use `git fetch -u`, so an existing local branch is updated when re-testing the same pull request. But not the more risky `git fetch -f` in to handle force pushes, as we don't want to accidentally overwrite important local changes. * Show different merge command depending on the chosen merge style, interactively updated.
* Show placeholder email in privacy popup (#27770)Gerd Katzenbeisser2023-10-251-1/+1
| | | | | | | | | | | | This PR will show the _noreply_ address in the privacy popup _keep_email_private_popup_. I had to look into the source code to figure out which E-Mail Adress I had to use on gitea.com to hide it from public access. According to the contribution guidelines I only updated the en-US translation file. Co-authored-by: Hakito <hakito@git.example.com>
* teams: new View button (#27685)tomholford2023-10-221-0/+1
| | | | | | | | | | | | | | | | | | | | | | Per the discussion on #22054, the flow for adding a new team member to an org is not intuitive for new Gitea users. The ideal solution would be to add a new button on the Org > Members index view (see the screenshot mockup in the issue description). However, this would require a refactor of the UX for the flow. The current flow has an implicit context of which team within the org the new member is being added to ('Owners' by default). From the Members index, there is no implicit context; the flow would have to add a picker for which team the new member should be added to. So, as a stopgap, this change simply adds a button to the Teams index page that performs the same action as clicking on the title of the team (a behavior that is currently too obscure as indicated in the comments on the issue). This should reduce support burden and serve as a decent temporary measure until the Add Member flow is refactored. --------- Co-authored-by: tomholford <tomholford@users.noreply.github.com>
generated by cgit v1.2.3 (git 2.39.1) at 2025-02-10 22:17:15 +0000