mirror of https://github.com/go-gitea/gitea.git synced 2024-11-20 12:04:36 +01:00

Git with a cup of tea, painless self-hosted git service https://gitea.io/

Go to file

Brad Albright 82be59e633 issue search on my related repositories (#9758 ) * adding search capability to user's issues dashboard * global issue search * placement of search bar on issues dashboard * fixed some bugs in the issue dashboard search * added unit test because IssueIDs option was added to UserIssueStatsOptions * some renaming of fields in the issue dashboard code to be more clear; also trying to fix issue of searching the right repos based on the filter * added unit test fro GetRepoIDsForIssuesOptions; fixed search lost on pagination; using shown issue status for open/close count; removed some debugging * fix issue with all count showing incorrectly * removed todo comment left in by mistake * typo pulling wrong count * fxied all count being off when selecting repositories * setting the opts.IsClosed after pulling repos to search, this is done so that the list of repo ids to serach for the keyword is not limited, we need to get all the issue ids for the shown issue stats * added "accessibleRepositoryCondition" check on the query to pull the repo ids to search for issues, this is an added protection to ensure we don't search repos the user does not have access to * added code so that in the issues search, we won't use an in clause of issues ids that goes over 1000 * fixed unit test * using 950 as the limit for issue search, removed unneeded group by in GetRepoIDsForIssuesOptions, showing search on pulls dashboard page too (not just issues) Co-authored-by: guillep2k <18600385+guillep2k@users.noreply.github.com>		2020-02-29 03:52:05 -03:00
.github
assets
cmd
contrib	make/pr: enforce vendor for run (#10296 )	2020-02-16 16:30:09 +00:00
custom/conf
docker
docs	Add max-file-size to LFS (#10463 )	2020-02-28 01:46:57 -03:00
integrations
models
modules
options
public
routers
scripts
services
snap
templates
vendor
web_src
.changelog.yml	Changelog 1.11.0 (#10204 ) (#10211 )	2020-02-10 11:16:31 -05:00
.drone.yml
.editorconfig
.eslintrc
.gitattributes
.gitignore
.golangci.yml
.ignore
.lgtm
.npmrc
.revive.toml
.stylelintrc
BSDmakefile	Add BSDmakefile to prevent errors when `make` is called under FreeBSD (#4446 )	2018-07-16 20:45:51 +02:00
CHANGELOG.md
CONTRIBUTING.md
DCO
Dockerfile
go.mod
go.sum
LICENSE	Fix typo	2016-11-08 08:42:05 +01:00
main.go
MAINTAINERS
Makefile
package-lock.json
package.json
README_ZH.md
README.md
semantic.json
tools.go
webpack.config.js

README.md

简体中文

Gitea - Git with a cup of tea

Purpose

The goal of this project is to make the easiest, fastest, and most painless way of setting up a self-hosted Git service. Using Go, this can be done with an independent binary distribution across all platforms which Go supports, including Linux, macOS, and Windows on x86, amd64, ARM and PowerPC architectures. Want to try it before doing anything else? Do it with the online demo! This project has been forked from Gogs since 2016.11 but changed a lot.

Building

From the root of the source tree, run:

TAGS="bindata" make build

or if sqlite support is required:

TAGS="bindata sqlite sqlite_unlock_notify" make build

The build target is split into two sub-targets:

make backend which requires Go 1.11 or greater.
make frontend which requires Node.js 10.0.0 or greater.

If pre-built frontend files are present it is possible to only build the backend:

	TAGS="bindata" make backend

More info: https://docs.gitea.io/en-us/install-from-source/

Using

./gitea web

NOTE: If you're interested in using our APIs, we have experimental support with documentation.

Contributing

Expected workflow is: Fork -> Patch -> Push -> Pull Request

NOTES:

YOU MUST READ THE CONTRIBUTORS GUIDE BEFORE STARTING TO WORK ON A PULL REQUEST.
If you have found a vulnerability in the project, please write privately to security@gitea.io. Thanks!

Further information

For more information and instructions about how to install Gitea, please look at our documentation. If you have questions that are not covered by the documentation, you can get in contact with us on our Discord server, or forum!