go-gitea / gitea

Git with a cup of tea! Painless self-hosted all-in-one software development service, including Git hosting, code review, team collaboration, package registry and CI/CD

Gitea

View this document in Chinese

Purpose

The goal of this project is to make the easiest, fastest, and most painless way of setting up a self-hosted Git service.

As Gitea is written in Go, it works across all the platforms and architectures that are supported by Go, including Linux, macOS, and Windows on x86, amd64, ARM and PowerPC architectures. This project has been forked from Gogs since November of 2016, but a lot has changed.

For online demonstrations, you can visit try.gitea.io.

For accessing free Gitea service (with a limited number of repositories), you can visit gitea.com.

To quickly deploy your own dedicated Gitea instance on Gitea Cloud, you can start a free trial at cloud.gitea.com.

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 Stable, the required version is defined in go.mod.
• make frontend which requires Node.js LTS or greater.

Internet connectivity is required to download the go and npm modules. When building from the official source tarballs which include pre-built frontend files, the frontend target will not be triggered, making it possible to build without Node.js.

More info: https://docs.gitea.com/installation/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

Note

1. YOU MUST READ THE CONTRIBUTORS GUIDE BEFORE STARTING TO WORK ON A PULL REQUEST.
2. If you have found a vulnerability in the project, please write privately to [email protected]. Thanks!

Translating

Translations are done through Crowdin. If you want to translate to a new language ask one of the managers in the Crowdin project to add a new language there.

You can also just create an issue for adding a language or ask on discord on the #translation channel. If you need context or find some translation issues, you can leave a comment on the string or ask on Discord. For general translation questions there is a section in the docs. Currently a bit empty but we hope to fill it as questions pop up.

https://docs.gitea.com/contributing/localization

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 create a post in the discourse forum.

We maintain a list of Gitea-related projects at gitea/awesome-gitea.

The official Gitea CLI is developed at gitea/tea.

Authors

• Maintainers
• Contributors
• Translators

Backers

Thank you to all our backers! 🙏 [Become a backer]

Sponsors

Support this project by becoming a sponsor. Your logo will show up here with a link to your website. [Become a sponsor]

FAQ

How do you pronounce Gitea?

Gitea is pronounced /ɡɪ’ti:/ as in "gi-tea" with a hard g.

Why is this not hosted on a Gitea instance?

We're working on it.

License

This project is licensed under the MIT License. See the LICENSE file for the full license text.

Screenshots

Looking for an overview of the interface? Check it out!

gitea's Issues

[Meta] Improvements to the API

Meta-issue for everything API related. Please don't close until API is done, and don't set a milestone either since it's long-running

Original Gogs-issue

Related Issues:

• CI/CD Status ( Gogs Issue )
• PR (#248)
• OAuth-support for API
  • Related Issue: #27
• Stars (WIP)
• Inconsistencies
  • Issue Comments
  • Issue Labels
  • PR JSON Object
• Releases New PR
• User/Org Repo Listing

Not APIs but related:

• RSS Support ( Gogs Issue )
  • Required for Activity Feed API
  • Version Notification
• Plugin Infrastructure
  • Should really go in go-gitea/proposals, drafts are already done.
• React UI
  • As I mentioned in that Issue, a complete API would allow others to implement their own UIs if necessary
  • Also ties in with #35

Will add more to this list as they keep coming.

This also requires us to fork gogits/go-gogs-client done 😄

---

Want to back this issue? Post a bounty on it! We accept bounties via Bountysource.

rewrite docker stuff

as gitea grows, we have to rewrite docker stuff in the docker dir.

this issue will stays open until PR is merged and will serve a repo for comments.

feel free to add what you think should be done regarding docker build

Moderation concept for issues on git repositories

Hi guys,

Open source projects is amazing, but sometimes, noob users usually more disturb than help and collaborate on issues.
Because this I think that is good idea to implement moderation option on issues, so repo owerns and moderators
may ban user on specific issue or on all repo issues.

Example, I want to ban octocat on my awesome-devops repo on "Add Puffin" because she is spamming on issue,
I can enable ban and put reason "you're not following the rules", then when octocat try to comment,
will not possible, because is banned and will display to octocat "You can't post on this issue, reason: you're not following the rules".

Like this, if octocat is banned on all repo, she can't open new issue and display too "You can't open this issue, reason: I don't like you".

This idea is to prevent this as example: git/git#233

This is only a concept, what you think guys?

Original idea: https://gist.github.com/joubertredrat/05759a27b71a4e2da72f9079edc9694b
Issue on GitLab: https://gitlab.com/gitlab-org/gitlab-ce/issues/19801

Reference: gogs/gogs#3658

Page with about Gitea project

Hi Guys,

Before create new version of Gitea, I think that create a page explaining the reasons to create Gitea fork from Gogs, so it will be easier to understand and accept our community project

Look this examples:
Observium ==(fork)=> LibreNMS: http://docs.librenms.org/General/Welcome-to-Observium-users/
Zpanel ==(fork)=> Sentora: http://sentora.org/about
ownCloud ==(fork)=> NextCloud: http://karlitschek.de/2016/06/nextcloud/

What you think guys?

Different users with same e-mail causes error on create repositores and user creation from register

• Gogs version (or commit ref): 0.9.97.0901
• Git version: 1.9.1
• Operating system: Ubuntu 14.04.5 LTS x64
• Database (use [x]):
  • PostgreSQL
  • MySQL
  • SQLite
• Can you reproduce the bug at https://try.gogs.io:
  • Yes (https://try.gogs.io/user/activate?code=2016092109210001800019682194a3e5a3bfe65a90bcd11eb7a010eea972656472617432)
  • No
  • Not relevant
• Log gist: https://gist.github.com/joubertredrat/7792a5e54410795c8cca270f96a4efe2

Description

I identified 2 issues about different users with same e-mail, one on my environment and other on demo.

On mine Gogs instance I have my one user provided by SMTP authentication with e-mail my@email. Today I created one local user with same e-mail my@email. After this, both users can't create repositories, as is in gist above. Other users can create repositories without problems.

For see if I can reproduce same problem, I go to test on Gogs demo, I created user redrat1 without problems. Then, I created user redrat2 with same email from redrat1. I received email to activate account, but If I try to enable user redrat2, causes error 500.

Reference: gogs/gogs#3681

--- Want to back this issue? **[Post a bounty on it!](https://www.bountysource.com/issues/38896692-different-users-with-same-e-mail-causes-error-on-create-repositores-and-user-creation-from-register?utm_campaign=plugin&utm_content=tracker%2F47456670&utm_medium=issues&utm_source=github)** We accept bounties via [Bountysource](https://www.bountysource.com/?utm_campaign=plugin&utm_content=tracker%2F47456670&utm_medium=issues&utm_source=github).

Externalize bindata.go to an auto-generated file

I think bindata.go dont have to be committed on repository and must be auto-generated during the make process.

It become a mess when two (or more) Pull Requests update different files (eg : app.ini for the first commit and add new files for the second) because the bindata.go file cause merge error each time.

Integrate an OAuth2 provider

To make it easier for other applications to hook into Gitea we should integrate an OAuth2 provider, that way tools like Drone CI can authenticate against Gitea much easier. A good library for that can be https://github.com/RangelReale/osin.

---

Want to back this issue? Post a bounty on it! We accept bounties via Bountysource.

Webhooks for issues

I will just add this here, from Gogs issues. Title is self explanatory, I think this is must have feature.

#2319

--- Want to back this issue? **[Post a bounty on it!](https://www.bountysource.com/issues/39116501-webhooks-for-issues?utm_campaign=plugin&utm_content=tracker%2F47456670&utm_medium=issues&utm_source=github)** We accept bounties via [Bountysource](https://www.bountysource.com/?utm_campaign=plugin&utm_content=tracker%2F47456670&utm_medium=issues&utm_source=github).

Milestone card view

Currently we can list the issues of one milestone, but I think if we can set some progress and provide a card view, we will manage it well. A milestone like a project on github. So if you create a milestone, you have created a project, it's no need an extra UI to do that.

Protected branches system

One missing feature from gogs is a way to protect branches like Github does.
After the completion of the API implementation, we could easily add application like Drone to check the PR.

The UI need to be changed to add options to protect branches like this:

I suggest to add some columns in table (don't know how many yet) to store those options.
The "Merge" button from a PR should be activated is the conditions are not matched.

---

Want to back this issue? Post a bounty on it! We accept bounties via Bountysource.

Embed bindata optionally

I would like to embed the bindata optionally based on a build tag, since we are running a Go application I really love the feature to server everything from the single file.

Loading progressbar on Gitea

Hi guys,

This is a small Feature suggestion for Gogs UX. On my projects, I use page loading progress bar and is simple to use, similar from Youtube, when page is loading, is possible to see loading progressbar on top page.

I use this plugin with theme Flash and worked very fine here.

What you think?

Reference: gogs/gogs#3693

--- Want to back this issue? **[Post a bounty on it!](https://www.bountysource.com/issues/38896725-loading-progressbar-on-gitea?utm_campaign=plugin&utm_content=tracker%2F47456670&utm_medium=issues&utm_source=github)** We accept bounties via [Bountysource](https://www.bountysource.com/?utm_campaign=plugin&utm_content=tracker%2F47456670&utm_medium=issues&utm_source=github).

Copyright on source in Gitea

Hi guys,

Gitea is fork from Gogs and we need to respect this, but, the plan is make this as independent fork, then, we need to copyright us too. In PHP project we refer to the old contributors, but also the new ones on comments.

The question is, we will add new copyright on comments as example or not?

// Copyright 2014-2016 The Gogs Authors. All rights reserved.
// Copyright 2016-2016 The Gogs and Gitea Authors. All rights reserved.
// Use of this source code is governed by a MIT-style
// license that can be found in the LICENSE file.

Let's talk

Support Matomo and Google analytics

Hi guys,

I think that Gitea can have support to Piwik or Google analytics. What you think?

--- Want to back this issue? **[Post a bounty on it!](https://www.bountysource.com/issues/38917746-support-to-piwik-and-google-analytics?utm_campaign=plugin&utm_content=tracker%2F47456670&utm_medium=issues&utm_source=github)** We accept bounties via [Bountysource](https://www.bountysource.com/?utm_campaign=plugin&utm_content=tracker%2F47456670&utm_medium=issues&utm_source=github).

Order milestone by asc or option to set milestones order

Hi guys,

I'm looking here that milestones and labels order is by insert, then I think that is good idea or show by asc or have option to repo owner define best order to display on manager or on issue.

Thanks.

Reference: gogs/gogs#3063

Translation process

I have ever gave this idea on Gogs. Now I give it again.

I think we can develop a language editor UI on admin panel. It could simple, there are two columns, left is English, right is another, he can select one from the supported languages above right column.
Every line is a translate, left is english word, right is the special language. After finished the translation, he can save it. After that, he can go and look at the UI immediately. Of course, if he like, he can download the locale file and send a PR to gitea repo.

Allow Gitea to have themes

Since we use semantic-ui and it can handle themes, Gitea should provide the default theme and a dark theme also.
Users will be able to make their own theme too.

I would suggest to begin with only css tweaks to change the display of pages.
In a second step, maybe we can add themes to modify templates file (.tmpl) to modify the links on each page.

What do you think about that?

--- Want to back this issue? **[Post a bounty on it!](https://www.bountysource.com/issues/38935464-allow-gitea-to-have-themes?utm_campaign=plugin&utm_content=tracker%2F47456670&utm_medium=issues&utm_source=github)** We accept bounties via [Bountysource](https://www.bountysource.com/?utm_campaign=plugin&utm_content=tracker%2F47456670&utm_medium=issues&utm_source=github).

Log option on admin area

Hi guys,

Sometimes I want to see Gogs logs to see if anything is wrong, but today I need to go to gogs log folder to see logs.

Then I think that is good idea to add a Logs options on Gogs admin area and display gogs.log, http.log, serv.log, update.log and other Gogs logs. With this will be possible to see logs on Gogs install more easy and to report issues too.

What you think guys?

Reference: gogs/gogs#3721

Integrate Drone CI

To keep the CI system as fast as possible we should replace TravisCI with Drone CI, we can use my hosted version or we can also run our own Drone CI instance, however we prefer.

Can't login with SMTP authentication

Hi guys,

Same issue here, if user already exists on base, login normal, but if doesn't exist user, get error on login.

[Macaron] 2016-11-01 14:42:07: Completed /user/login 500 Internal Server Error in 1.364496ms

Reference: gogs/gogs#3824

Detection of renamed files not working with Git 1.9.1

• Gitea version (or commit ref): 0.9.99.0903
• Git version: 1.9.1
• Operating system: Ubuntu 14.04.5 LTS
• Database:
  • PostgreSQL
  • MySQL
  • SQLite

Description

I have a commit with a file A which get's renamed to B. Instead of showing that, Gogs/Gitea just shows me A with all it content removed and added again.

This Gogs commit added support for detecting file renames: bc82157

I couldn't reproduce this on https://try.gogs.io, so I think it has something to do with my older Git version.

option to add and remove all repositories on team

Hi guys,

I have this scenario, I have a "razer" (fictitious) organization with 20 repositories, I created new team called "staff" and I want to add all repositories on this team. Today I need to add manually 20 times the repo on team.

I think that is good idea to have two buttons "add all repositories" and "remove all repositories", with this is easy if I need to add or remove all in one time.

This resource is good to use to add and remove all users too.

What you think guys? :)

Reference: gogs/gogs#3028

Closer Github UI look

When we have a look to Gitea compared to Github it's look alike but there are several color and menu ui tweak that still need to be done.

On the other hand, semantic ui provide a good template that look like Github better than Gitea do.
I think an improvement can be done around semantic to see why Gitea doesn't seems to look as it should.
Maybe an update of the vendor css or something else.

After this step, the theming feature should be a plus (I will make another issue for that).

Testability Strategy

Reference #2293

Basically, we need more tests 😄

Should this go in go-gitea/proposals instead?

---

Want to back this issue? Post a bounty on it! We accept bounties via Bountysource.

Resurrection?

Sometimes ago gitea closed, because author of gogs merge some or and continue to develop it.
Why gitea now resurrected again?

Move useless comments from source to Issues

Running make fixme todo will print a nice list of TODO/FIXME-comments from source files. These should be moved to proper issues so that they can be 1) tracked and 2) people actually know about them 😆

There are more instances of these comments throughout the code, and those should be moved as well.

Thoughts?

--- Want to back this issue? **[Post a bounty on it!](https://www.bountysource.com/issues/38952940-move-useless-comments-from-source-to-issues?utm_campaign=plugin&utm_content=tracker%2F47456670&utm_medium=issues&utm_source=github)** We accept bounties via [Bountysource](https://www.bountysource.com/?utm_campaign=plugin&utm_content=tracker%2F47456670&utm_medium=issues&utm_source=github).

Integrate dependency manager

We have already talked about that on Gitter, we want to include the dependencies and we want to manage the dependencies with govendor, so let's integrate it!

Housekeeping

It would be nice to have a button (on each repos settings page) to run a housekeeping operation. This operation is useful to clean a repository and decrease is size.

Usually these two commands are run:

git prune
git gc --aggressive

--- Want to back this issue? **[Post a bounty on it!](https://www.bountysource.com/issues/38979600-housekeeping?utm_campaign=plugin&utm_content=tracker%2F47456670&utm_medium=issues&utm_source=github)** We accept bounties via [Bountysource](https://www.bountysource.com/?utm_campaign=plugin&utm_content=tracker%2F47456670&utm_medium=issues&utm_source=github).

Update contributing guideline

We should update the files located at .github directory to reflect the new community approach. We should also write about our processes with 2 required reviews, usage of LGTM and so on.

Update startup scripts to use "gitea" instead of "gogs"

Subject says it all

Contribution system: History heatmap for user

Hi guys,

I think that is a possible feature, a history heatmap similar to github or gitlab.
Actually exists a plugin called Calendar HeatMap. I used this on mine project to heat application log and worked fine here.
Then, is only a idea, what you think? :)

http://cal-heatmap.com/
https://github.com/wa0x6e/cal-heatmap

Reference: gogs/gogs#1640

Replace all GOGS_* variables

The title already says everything, there are still variables with this making schema.

Fix linting error

Currently the go linter errors out on various places, we should fix that to increase the code quality.

Provide releases and deb/rpm packages via Bintray

I would like to integrate a proper process to create real system packages and distribute them via Bintray, than users can just add a deb/rpm repository and got a clean upgrade path.

Beside that we can also publish our releases to a static page or also to Bintray for download.

Web editor indentation

Now with web editor working fine, I think that is necessary to set configurations by default or defined by user for better experience with web editor.

On PHP, javascript and I think that Go (Unknwon talk me if I'm wrong) we prefer 4 spaces indentation.
However, HTML and CSS developers normally prefer 2 spaces indentation. Have cases on other developers prefer tabulation instead spaces.

Because this I think that web editor can be configurable, one good example for this is on Bitbucket, you can set options in own editor.

Or this configuration can be defined on user settings on only on admin area.

What you think guys?

Reference: gogs/gogs#3460 (comment)
Reference: gogs/gogs#3610

--- Want to back this issue? **[Post a bounty on it!](https://www.bountysource.com/issues/38896626-web-editor-indentation?utm_campaign=plugin&utm_content=tracker%2F47456670&utm_medium=issues&utm_source=github)** We accept bounties via [Bountysource](https://www.bountysource.com/?utm_campaign=plugin&utm_content=tracker%2F47456670&utm_medium=issues&utm_source=github).

Integrate badges of services

I would suggest to include a specific amount of badges, I would suggest a list of these:

• DroneCI, like
• Codecov.io, like
• Go report, like
• Go doc, like
• Docker, like
• Gitter, like

Anything that I missed?

Support to Last login

Hi guys,

This issue #8 propose option to have more control to admin, but don't have plans for this concept.

As alternative, I think that is possible to add one field on user only to set last time login for first Gitea release. What you think guys?

display page revisions on wiki

Hi guys,

Wiki on Gogs is very fine, I liked a lot, but I think that is good idea to be possible see other revisions from page as a page history.

What you think?

Reference: gogs/gogs#2991

Integrate an OAuth2 consumer

To keep the barrier of Gitea as small as possible we should integrate an OAuth2 consumer. That way new users can register with just a few clicks and can reuse there already elsewhere existing accounts. A good library for that can be https://github.com/markbates/goth.

---

Want to back this issue? Post a bounty on it! We accept bounties via Bountysource.

Commits and pull files

Before we can start a review, we can implement comment on one line of PRs at first.
I think this includes two sub issues.

• Commit comment #3748 see #4898
• Pull files comment #3748

Automatically generated version on build

I think we can learn Golang's version management.

On master, all the version numbers will be gave on build and the version number is the commit hash. Since the hash is too long, we can use the first 7 characters. i.e. tip+2b445c7

On release branch, all the version number will be gave on build and the version number is branch name plus git hash. i.e. 1.0+2b445c7

For a tag version i.e. 1.0.0, the version number could be static and we can give it a special number not a git hash.

So that, when a user report an issue, we can know the question is from which version quickly.

Docker testsuite for gitea builds

refering gitter discussion.

the idea here is to have for docker builds unit and functionnal testing.
these could use for example:

• hadolint to validate dockerfile syntax
• serverspec for unit and functionnal testing.

the overall is to provide best quality build regarding docker builds.

comments welcome of course :)

--- Want to back this issue? **[Post a bounty on it!](https://www.bountysource.com/issues/39025480-docker-testsuite-for-gitea-builds?utm_campaign=plugin&utm_content=tracker%2F47456670&utm_medium=issues&utm_source=github)** We accept bounties via [Bountysource](https://www.bountysource.com/?utm_campaign=plugin&utm_content=tracker%2F47456670&utm_medium=issues&utm_source=github).

Responsive UI

We should provide a responsive UI on best afford. The best way should be a separate view like it's done on gitHub, but on the short term we could simply provide repsonsive elements to give a good view also on mobile devices.

---

Want to back this issue? Post a bounty on it! We accept bounties via Bountysource.

[WIP] Gitea deployment examples

Add deployment examples of gitea.

For now :
vagrant
docker compose
kubernetes

---

Want to back this issue? Post a bounty on it! We accept bounties via Bountysource.

Replace gogits go-gogs-client with go-sdk

We want to replace gogits/go-gogs-client with go-gitea/go-sdk, below you can see a greped list of values. Please keep in mind that we also need to update our client repository.

# grep -R go-gogs-client *
README.md:5. If you're interested in using APIs, we have experimental support with [documentation](https://github.com/gogits/go-gogs-client/wiki).
models/action.go:	api "github.com/gogits/go-gogs-client"
models/issue.go:	api "github.com/gogits/go-gogs-client"
models/issue_comment.go:	api "github.com/gogits/go-gogs-client"
models/issue_label.go:	api "github.com/gogits/go-gogs-client"
models/pull.go:	api "github.com/gogits/go-gogs-client"
models/repo.go:	api "github.com/gogits/go-gogs-client"
models/user.go:	api "github.com/gogits/go-gogs-client"
models/webhook.go:	api "github.com/gogits/go-gogs-client"
models/webhook_slack.go:	api "github.com/gogits/go-gogs-client"
modules/base/base.go:const DOC_URL = "https://github.com/gogits/go-gogs-client/wiki"
routers/api/v1/admin/org.go:	api "github.com/gogits/go-gogs-client"
routers/api/v1/admin/org.go:// https://github.com/gogits/go-gogs-client/wiki/Administration-Organizations#create-a-new-organization
routers/api/v1/admin/org_team.go:	api "github.com/gogits/go-gogs-client"
routers/api/v1/admin/repo.go:	api "github.com/gogits/go-gogs-client"
routers/api/v1/admin/repo.go:// https://github.com/gogits/go-gogs-client/wiki/Administration-Repositories#create-a-new-repository
routers/api/v1/admin/user.go:	api "github.com/gogits/go-gogs-client"
routers/api/v1/admin/user.go:// https://github.com/gogits/go-gogs-client/wiki/Administration-Users#create-a-new-user
routers/api/v1/admin/user.go:// https://github.com/gogits/go-gogs-client/wiki/Administration-Users#edit-an-existing-user
routers/api/v1/admin/user.go:// https://github.com/gogits/go-gogs-client/wiki/Administration-Users#delete-a-user
routers/api/v1/admin/user.go:// https://github.com/gogits/go-gogs-client/wiki/Administration-Users#create-a-public-key-for-user
routers/api/v1/api.go:	api "github.com/gogits/go-gogs-client"
routers/api/v1/convert/convert.go:	api "github.com/gogits/go-gogs-client"
routers/api/v1/misc/markdown.go:	api "github.com/gogits/go-gogs-client"
routers/api/v1/misc/markdown.go:// https://github.com/gogits/go-gogs-client/wiki/Miscellaneous#render-an-arbitrary-markdown-document
routers/api/v1/misc/markdown.go:// https://github.com/gogits/go-gogs-client/wiki/Miscellaneous#render-a-markdown-document-in-raw-mode
routers/api/v1/org/org.go:	api "github.com/gogits/go-gogs-client"
routers/api/v1/org/org.go:// https://github.com/gogits/go-gogs-client/wiki/Organizations#list-your-organizations
routers/api/v1/org/org.go:// https://github.com/gogits/go-gogs-client/wiki/Organizations#list-user-organizations
routers/api/v1/org/org.go:// https://github.com/gogits/go-gogs-client/wiki/Organizations#get-an-organization
routers/api/v1/org/org.go:// https://github.com/gogits/go-gogs-client/wiki/Organizations#edit-an-organization
routers/api/v1/org/team.go:	api "github.com/gogits/go-gogs-client"
routers/api/v1/repo/branch.go:	api "github.com/gogits/go-gogs-client"
routers/api/v1/repo/branch.go:// https://github.com/gogits/go-gogs-client/wiki/Repositories#get-branch
routers/api/v1/repo/branch.go:// https://github.com/gogits/go-gogs-client/wiki/Repositories#list-branches
routers/api/v1/repo/collaborators.go:	api "github.com/gogits/go-gogs-client"
routers/api/v1/repo/file.go:// https://github.com/gogits/go-gogs-client/wiki/Repositories-Contents#download-raw-content
routers/api/v1/repo/file.go:// https://github.com/gogits/go-gogs-client/wiki/Repositories-Contents#download-archive
routers/api/v1/repo/hook.go:	api "github.com/gogits/go-gogs-client"
routers/api/v1/repo/hook.go:// https://github.com/gogits/go-gogs-client/wiki/Repositories#list-hooks
routers/api/v1/repo/hook.go:// https://github.com/gogits/go-gogs-client/wiki/Repositories#create-a-hook
routers/api/v1/repo/hook.go:// https://github.com/gogits/go-gogs-client/wiki/Repositories#edit-a-hook
routers/api/v1/repo/issue.go:	api "github.com/gogits/go-gogs-client"
routers/api/v1/repo/issue_comment.go:	api "github.com/gogits/go-gogs-client"
routers/api/v1/repo/issue_label.go:	api "github.com/gogits/go-gogs-client"
routers/api/v1/repo/key.go:	api "github.com/gogits/go-gogs-client"
routers/api/v1/repo/key.go:// https://github.com/gogits/go-gogs-client/wiki/Repositories-Deploy-Keys#list-deploy-keys
routers/api/v1/repo/key.go:// https://github.com/gogits/go-gogs-client/wiki/Repositories-Deploy-Keys#get-a-deploy-key
routers/api/v1/repo/key.go:// https://github.com/gogits/go-gogs-client/wiki/Repositories-Deploy-Keys#add-a-new-deploy-key
routers/api/v1/repo/key.go:// https://github.com/gogits/go-gogs-client/wiki/Repositories-Deploy-Keys#remove-a-deploy-key
routers/api/v1/repo/label.go:	api "github.com/gogits/go-gogs-client"
routers/api/v1/repo/milestone.go:	api "github.com/gogits/go-gogs-client"
routers/api/v1/repo/repo.go:	api "github.com/gogits/go-gogs-client"
routers/api/v1/repo/repo.go:// https://github.com/gogits/go-gogs-client/wiki/Repositories#search-repositories
routers/api/v1/repo/repo.go:// https://github.com/gogits/go-gogs-client/wiki/Repositories#list-your-repositories
routers/api/v1/repo/repo.go:// https://github.com/gogits/go-gogs-client/wiki/Repositories#create
routers/api/v1/repo/repo.go:// https://github.com/gogits/go-gogs-client/wiki/Repositories#migrate
routers/api/v1/repo/repo.go:// https://github.com/gogits/go-gogs-client/wiki/Repositories#get
routers/api/v1/repo/repo.go:// https://github.com/gogits/go-gogs-client/wiki/Repositories#delete
routers/api/v1/user/app.go:	api "github.com/gogits/go-gogs-client"
routers/api/v1/user/app.go:// https://github.com/gogits/go-gogs-client/wiki/Users#list-access-tokens-for-a-user
routers/api/v1/user/app.go:// https://github.com/gogits/go-gogs-client/wiki/Users#create-a-access-token
routers/api/v1/user/email.go:	api "github.com/gogits/go-gogs-client"
routers/api/v1/user/email.go:// https://github.com/gogits/go-gogs-client/wiki/Users-Emails#list-email-addresses-for-a-user
routers/api/v1/user/email.go:// https://github.com/gogits/go-gogs-client/wiki/Users-Emails#add-email-addresses
routers/api/v1/user/email.go:// https://github.com/gogits/go-gogs-client/wiki/Users-Emails#delete-email-addresses
routers/api/v1/user/follower.go:	api "github.com/gogits/go-gogs-client"
routers/api/v1/user/follower.go:// https://github.com/gogits/go-gogs-client/wiki/Users-Followers#list-followers-of-a-user
routers/api/v1/user/follower.go:// https://github.com/gogits/go-gogs-client/wiki/Users-Followers#list-users-followed-by-another-user
routers/api/v1/user/follower.go:// https://github.com/gogits/go-gogs-client/wiki/Users-Followers#check-if-you-are-following-a-user
routers/api/v1/user/follower.go:// https://github.com/gogits/go-gogs-client/wiki/Users-Followers#check-if-one-user-follows-another
routers/api/v1/user/follower.go:// https://github.com/gogits/go-gogs-client/wiki/Users-Followers#follow-a-user
routers/api/v1/user/follower.go:// https://github.com/gogits/go-gogs-client/wiki/Users-Followers#unfollow-a-user
routers/api/v1/user/key.go:	api "github.com/gogits/go-gogs-client"
routers/api/v1/user/key.go:// https://github.com/gogits/go-gogs-client/wiki/Users-Public-Keys#list-your-public-keys
routers/api/v1/user/key.go:// https://github.com/gogits/go-gogs-client/wiki/Users-Public-Keys#list-public-keys-for-a-user
routers/api/v1/user/key.go:// https://github.com/gogits/go-gogs-client/wiki/Users-Public-Keys#get-a-single-public-key
routers/api/v1/user/key.go:// https://github.com/gogits/go-gogs-client/wiki/Users-Public-Keys#create-a-public-key
routers/api/v1/user/key.go:// https://github.com/gogits/go-gogs-client/wiki/Users-Public-Keys#delete-a-public-key
routers/api/v1/user/user.go:	api "github.com/gogits/go-gogs-client"
routers/repo/webhook.go:	api "github.com/gogits/go-gogs-client"
routers/repo/webhook.go:	ctx.Data["Description"] = ctx.Tr("repo.settings.hooks_desc", "https://github.com/gogits/go-gogs-client/wiki/Repositories-Webhooks")
templates/repo/create.tmpl:						<label>{{.i18n.Tr "repo.readme"}} <a target="_blank" href="https://github.com/gogits/go-gogs-client/wiki/Repositories#litte-notes-on-readme-template"><span class="octicon octicon-question"></span></a></label>
vendor/vendor.json:			"path": "github.com/gogits/go-gogs-client",

audit logs

Hi,

I think that is good idea to have user operation log to admin see what the user is doing at Gogs. Similar to example below

user	operation	information
joubertredrat	repo.create	Create repo MyProjectData
joubertredrat	user.settings	Edit settings
tboerger	repo.fork	Create Fork from MyProjectData to ForkMyProjectData
bkcsoft	repo.remove	Remove repo MySource
tboerger	admin.auth	Edit auth LDAP org-connection

This resource can be used on user page too, as user activity, set that log row is public (repo.) or private (user., admin.*) and display only public activity.

What you think?

Chat summary from March 14, 2017

References:
gogs/gogs#3016

Readme update

we should update logo and description at least in the README.MD

Support to test send e-mail from SMTP config

Hi guys,

Gitea (Gogs) have option to set SMTP as MTA, but don't have area to test if e-mail will be send. Today I need to use "forgot password" to see if SMTP is working properly.

I think that is good idea to add a option to send e-mail in admin area and simple send "Hello world" or other simple mail, this will help Gitea owner to see if is working fine configuration.

Implement git-lfs

Implementing git-lfs into gogs/gitea would be awesome for devs dealing with lots of binary files: https://git-lfs.github.com/

Ideally, it should be possible to

• pull&push lfs objects via https and ssh
• configure the directory used to store lfs objects on the server
• automatically remove unused lfs objects if a repository gets deleted on the server

Replace gogits git-module dependency

We want to replace the current dependency to gogits/git-module with go-gitea/git, below you can see a list of greped values.

# grep -R git-module *
cmd/serve.go:	git "github.com/gogits/git-module"
models/action.go:	"github.com/gogits/git-module"
models/git_diff.go:	"github.com/gogits/git-module"
models/git_diff.go:// TODO: move this function to gogits/git-module
models/git_diff.go:// TODO: move this function to gogits/git-module
models/pull.go:	"github.com/gogits/git-module"
models/release.go:	"github.com/gogits/git-module"
models/repo.go:	git "github.com/gogits/git-module"
models/repo_branch.go:	"github.com/gogits/git-module"
models/repo_editor.go:	git "github.com/gogits/git-module"
models/update.go:	git "github.com/gogits/git-module"
models/user.go:	"github.com/gogits/git-module"
models/webhook_slack.go:	"github.com/gogits/git-module"
models/wiki.go:	"github.com/gogits/git-module"
modules/context/repo.go:	"github.com/gogits/git-module"
routers/api/v1/convert/convert.go:	"github.com/gogits/git-module"
routers/api/v1/repo/file.go:	"github.com/gogits/git-module"
routers/install.go:	"github.com/gogits/git-module"
routers/repo/commit.go:	"github.com/gogits/git-module"
routers/repo/download.go:	"github.com/gogits/git-module"
routers/repo/editor.go:	"github.com/gogits/git-module"
routers/repo/http.go:	git "github.com/gogits/git-module"
routers/repo/middlewares.go:	"github.com/gogits/git-module"
routers/repo/pull.go:	"github.com/gogits/git-module"
routers/repo/repo.go:	"github.com/gogits/git-module"
routers/repo/setting.go:	"github.com/gogits/git-module"
routers/repo/view.go:	"github.com/gogits/git-module"
routers/repo/webhook.go:	git "github.com/gogits/git-module"
routers/repo/wiki.go:	"github.com/gogits/git-module"
vendor/vendor.json:			"path": "github.com/gogits/git-module",