## Checklist
The [contributor guide](https://forgejo.org/docs/next/contributor/) contains information that will be helpful to first time contributors. All work and communication must conform to Forgejo's [AI Agreement](https://codeberg.org/forgejo/governance/src/branch/main/AIAgreement.md). 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).
### Compliance
- [x] I confirm that I make this contribution in accordance with [Forgejo's AI Agreement](9084720dc6/AIAgreement.md).
### Tests for Go changes
- 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 ran...
- [x] `make pr-go` before pushing
### Documentation
- [x] added swagger documentation with this pull request
- [ ] 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
- [x] This change will be noticed by a Forgejo user or admin (feature, bug fix, performance, etc.). I suggest to include a release note for this change.
- [ ] This change is not visible to a Forgejo user or admin (refactor, dependency upgrade, etc.). I think there is no need to add a release note for this change.
*The decision if the pull request will be shown in the release notes is up to the mergers / release team.*
The content of the `release-notes/<pull request number>.md` file will serve as the basis for the release notes. If the file does not exist, the title of the pull request will be used instead.
<!--start release-notes-assistant-->
## Release notes
<!--URL:https://codeberg.org/forgejo/forgejo-->
- Features
- [PR](https://codeberg.org/forgejo/forgejo/pulls/14959): <!--number 14959 --><!--line 0 --><!--description ZmVhdChhcGkpOiByZXBvc2l0b3J5IHNlYXJjaCBieSBsYW5ndWFnZQ==-->feat(api): repository search by language<!--description-->
<!--end release-notes-assistant-->
Co-authored-by: kari_nord <kari_nord>
Reviewed-on: https://codeberg.org/forgejo/forgejo/pulls/14959
Reviewed-by: Andreas Ahlenstorf <aahlenst@noreply.codeberg.org>
Hi there! Tired of big platforms playing monopoly?
Providing Git hosting for your project, friends, company or community?
Forgejo (/for'd͡ʒe.jo/ inspired by forĝejo – the Esperanto word for forge) has you covered with its intuitive interface,
light and easy hosting and a lot of built-in functionality.
Forgejo was created in 2022
because we think that the project should be owned by an independent community.
If you second that, then Forgejo is for you!
Our promise: Independent Free/Libre Software forever!
What does Forgejo offer?
If you like any of the following, Forgejo is literally meant for you:
Lightweight: Forgejo can easily be hosted on nearly every machine.
Running on a Raspberry? Small cloud instance? No problem!
Project management: Besides Git hosting, Forgejo offers issues,
pull requests, wikis, kanban boards and much more to coordinate with your team.
Publishing: Have something to share? Use releases to host your software for download,
or use the package registry to publish it for docker, npm and many other package managers.
Customizable: Want to change your look? Change some settings?
There are many config switches to make Forgejo work exactly like you want.
Powerful: Organizations & team permissions, CI integration, Code Search, LDAP, OAuth and much more.
If you have advanced needs, Forgejo has you covered.
Privacy: From update checker to default settings: Forgejo is built to be privacy first for you and your crew.
Federation: (WIP) We are actively working to connect software forges with each other through ActivityPub,
and create a collaborative network of personal instances.
Forgejo is distributed under the terms of the GPL version 3.0 or any later version.
The agreement for this license was documented in June 2023 and implemented during the development of Forgejo v9.0. All Forgejo versions before v9.0 are distributed under the MIT license.
Get involved
If you are interested in making Forgejo better, either by reporting a bug or by changing the governance, please take a look at the contribution guide.
4635883acd
