summaryrefslogtreecommitdiffstats
path: root/templates (unfollow)
Commit message (Collapse)AuthorFilesLines
2024-11-25Add Low German to list of default languagesBenedikt Straub2-2/+3
2024-11-25Update dependency sortablejs to v1.15.4Renovate Bot2-5/+5
2024-11-25Lock file maintenanceRenovate Bot3-202/+207
2024-11-25Update renovate to v39.28.0 (forgejo) (#6065)Renovate Bot2-2/+2
Co-authored-by: Renovate Bot <forgejo-renovate-action@forgejo.org> Co-committed-by: Renovate Bot <forgejo-renovate-action@forgejo.org>
2024-11-24Show page titles in wiki search results (#6048)Oto Šťáva4-6/+41
Replace wiki page filenames with page titles in the search results, fixing the problem with them showing unreadable URI-encoded names.
2024-11-24Update module github.com/stretchr/testify to v1.10.0Renovate Bot2-3/+3
2024-11-23fix: Do not delete global Oauth2 applicationsOtto Richter1-0/+2
2024-11-23test: Global OAuth should not be deletedOtto Richter2-0/+9
Expected to fail: Global (instance-wide) OAuth application should not be deleted, but it is
2024-11-23fix: Preview picture not visible on Markdown file (#5781)Nirmal Kumar R9-19/+92
Extend API MarkupOptions to contain branch path. The `api.MarkupOptions{}` to have `BranchPath` which contains the current branch. The `RenderMarkup` function utilizes a struct since there are too many variables passed as arguments and that is not a good sign for readability. And `repo-editor.js` will contain a new form data which is `branch-path` which will then be utilized by `edit.tmpl` as `data-branch-path`. Closes: #4510 ## Checklist The [contributor guide](https://forgejo.org/docs/next/contributor/) contains information that will be helpful to first time contributors. There also are a few [conditions for merging Pull Requests in Forgejo repositories](https://codeberg.org/forgejo/governance/src/branch/main/PullRequestsAgreement.md). You are also welcome to join the [Forgejo development chatroom](https://matrix.to/#/#forgejo-development:matrix.org). ### Tests - I added test coverage for Go changes... - [ ] in their respective `*_test.go` for unit tests. - [ ] in the `tests/integration` directory if it involves interactions with a live Forgejo server. - I added test coverage for JavaScript changes... - [ ] in `web_src/js/*.test.js` if it can be unit tested. - [x] in `tests/e2e/*.test.e2e.js` if it requires interactions with a live Forgejo server (see also the [developer guide for JavaScript testing](https://codeberg.org/forgejo/forgejo/src/branch/forgejo/tests/e2e/README.md#end-to-end-tests)). ### Documentation - [ ] I created a pull request [to the documentation](https://codeberg.org/forgejo/docs) to explain to Forgejo users how to use this change. - [ ] I did not document these changes and I do not expect someone else to do it. ### Release notes - [ ] I do not want this change to show in the release notes. - [x] I want the title to show in the release notes with a link to this pull request. - [ ] I want the content of the `release-notes/<pull request number>.md` to be be used for the release notes instead of the title. Reviewed-on: https://codeberg.org/forgejo/forgejo/pulls/5781 Reviewed-by: Earl Warren <earl-warren@noreply.codeberg.org> Co-authored-by: Nirmal Kumar R <tildezero@gmail.com> Co-committed-by: Nirmal Kumar R <tildezero@gmail.com>
2024-11-22test: fix e2e testMichael Kriese1-1/+1
2024-11-22ci: use more `tmpfs` and `noatime` for faster CIMichael Kriese2-6/+18
2024-11-21i18n: update of translations from Codeberg Translate (#5960)Codeberg Translate11-277/+409
Co-authored-by: yumechi <yumechi@users.noreply.translate.codeberg.org> Co-authored-by: Edgarsons <Edgarsons@users.noreply.translate.codeberg.org> Co-authored-by: xtex <xtexchooser@duck.com> Co-authored-by: SomeTr <SomeTr@users.noreply.translate.codeberg.org> Co-authored-by: artnay <artnay@users.noreply.translate.codeberg.org> Co-authored-by: Fjuro <fjuro@alius.cz> Co-authored-by: 0ko <0ko@users.noreply.translate.codeberg.org> Co-authored-by: Benedikt Straub <Nordfriese@users.noreply.translate.codeberg.org> Co-authored-by: Atul_Eterno <Atul_Eterno@users.noreply.translate.codeberg.org> Co-authored-by: Atalanttore <Atalanttore@users.noreply.translate.codeberg.org> Co-authored-by: Juno Takano <jutty@users.noreply.translate.codeberg.org> Reviewed-on: https://codeberg.org/forgejo/forgejo/pulls/5960 Reviewed-by: 0ko <0ko@noreply.codeberg.org> Co-authored-by: Codeberg Translate <translate@noreply.codeberg.org> Co-committed-by: Codeberg Translate <translate@noreply.codeberg.org>
2024-11-21feat: add setting to block disposable emailsJames Hatfield5-11/+4173
- Add a new setting `EMAIL_DOMAIN_BLOCK_DISPOSABLE` that will append a list of domains that are known for being used by temporary or disposable email services. - Add a utility to automatically download and format the list of domains from the disposable-email-domains project on github. (https://github.com/disposable-email-domains/disposable-email-domains) license: CC0 1.0 Universal (CC0 1.0) [Public Domain] from README: """ This repo contains a list of disposable and temporary email address domains often used to register dummy users in order to spam or abuse some services. We cannot guarantee all of these can still be considered disposable but we do basic checking so chances are they were disposable at one point in time. """
2024-11-20chore(ci): remove unused experimental DNS updatesEarl Warren1-17/+0
2024-11-20fix: Allow Organisations to remove the Email Address (#5517)JakobDev8-10/+228
It is possible to set a Email for a Organization. This Email is optional and only used to be displayed on the profile page. However, once you set an EMail, you can no longer remove it. This PR fixes that. While working on the tests, I found out, that the API returns a 500 when trying to set an invalid EMail. I fixed that too. It returns a 422 now. Fixes #4567 Reviewed-on: https://codeberg.org/forgejo/forgejo/pulls/5517 Reviewed-by: Gusted <gusted@noreply.codeberg.org> Reviewed-by: Otto <otto@codeberg.org> Co-authored-by: JakobDev <jakobdev@gmx.de> Co-committed-by: JakobDev <jakobdev@gmx.de>
2024-11-19Fix regression from #4753JakobDev2-2/+30
2024-11-19fix(ui): apply smaller padding to comment headers0ko1-1/+4
2024-11-19ui: improve git notes0ko3-8/+9
2024-11-19Update dependency chartjs-plugin-zoom to v2.1.0Renovate Bot2-5/+12
2024-11-18[FEAT]Allow changing git notes (#4753)JakobDev17-14/+562
Git has a cool feature called git notes. It allows adding a text to a commit without changing the commit itself. Forgejo already displays git notes. With this PR you can also now change git notes. <details> <summary>Screenshots</summary> ![grafik](/attachments/53a9546b-c4db-4b07-92ae-eb15b209b21d) ![grafik](/attachments/1bd96f2c-6178-45d2-93d7-d19c7cbe5898) ![grafik](/attachments/9ea73623-25d1-4628-a43f-f5ecbd431788) ![grafik](/attachments/efea0c9e-43c6-4441-bb7e-948177bf9021) </details> ## Checklist The [developer guide](https://forgejo.org/docs/next/developer/) contains information that will be helpful to first time contributors. There also are a few [conditions for merging Pull Requests in Forgejo repositories](https://codeberg.org/forgejo/governance/src/branch/main/PullRequestsAgreement.md). You are also welcome to join the [Forgejo development chatroom](https://matrix.to/#/#forgejo-development:matrix.org). ### Tests - I added test coverage for Go changes... - [ ] in their respective `*_test.go` for unit tests. - [x] in the `tests/integration` directory if it involves interactions with a live Forgejo server. - I added test coverage for JavaScript changes... - [ ] in `web_src/js/*.test.js` if it can be unit tested. - [ ] in `tests/e2e/*.test.e2e.js` if it requires interactions with a live Forgejo server (see also the [developer guide for JavaScript testing](https://codeberg.org/forgejo/forgejo/src/branch/forgejo/tests/e2e/README.md#end-to-end-tests)). ### Documentation - [ ] I created a pull request [to the documentation](https://codeberg.org/forgejo/docs) to explain to Forgejo users how to use this change. - [x] I did not document these changes and I do not expect someone else to do it. ### Release notes - [ ] I do not want this change to show in the release notes. - [x] I want the title to show in the release notes with a link to this pull request. - [ ] I want the content of the `release-notes/<pull request number>.md` to be be used for the release notes instead of the title. <!--start release-notes-assistant--> ## Release notes <!--URL:https://codeberg.org/forgejo/forgejo--> - Features - [PR](https://codeberg.org/forgejo/forgejo/pulls/4753): <!--number 4753 --><!--line 0 --><!--description QWxsb3cgY2hhbmdpbmcgZ2l0IG5vdGVz-->Allow changing git notes<!--description--> <!--end release-notes-assistant--> Reviewed-on: https://codeberg.org/forgejo/forgejo/pulls/4753 Reviewed-by: Gusted <gusted@noreply.codeberg.org> Co-authored-by: JakobDev <jakobdev@gmx.de> Co-committed-by: JakobDev <jakobdev@gmx.de>
2024-11-18Escaping specific markdown in commit messages on Discord-type embeds #3664 ↵Marco De Araujo3-0/+145
(#5811) Co-authored-by: Marco De Araujo <marco.araujo.junior@gmail.com> Co-committed-by: Marco De Araujo <marco.araujo.junior@gmail.com>
2024-11-18chore(ci): merge jobs in issue-labels.yml in one workflowEarl Warren1-32/+38
Fixes: forgejo/forgejo#5999
2024-11-18chore(ci): cat all issue labels workflows in issue-labels.ymlEarl Warren5-199/+199
cat cascade-setup-end-to-end.yml backport.yml merge-requirements.yml release-notes-assistant.yml > issue-labels.yml rm cascade-setup-end-to-end.yml backport.yml merge-requirements.yml release-notes-assistant.yml