Repository navigation
Open
Labels
topic/deploymenttype/proposalThe new feature has not been accepted yet but needs to be discussed first.The new feature has not been accepted yet but needs to be discussed first.
Description
For the first big stage, we would like Gitea's development could be based on a Gitea hosted and github will only a mirror. This will maybe completed in v1.x. So that this issue will list all the features needed to be implemented before v1.x. And of course please discuss them and change my post.
-
Squash merge (Pull request merge strategy #712 Add Pull Request merge options - Ignore white-space for conflict checking, Rebase, Squash merge #3188) -
Complete Protected branch (Protected branches system #32 Protected branches system #339) -
Complete API support ([Meta] Improvements to the API #64) -
API Documents (API documentation for endpoint #194) -
Webhooks implementation (Webhooks implementation #2418) -
Better CI Integration ( (PR Status-API #1332))Drone PR: (OS thread limit reached while compiling from source #2017) -
Comment on commit and PR (Commits and pull files #124Comments on pull files #2583Pull request review/approval and comment on code #3748 ) -
Approvals system (Permissions to accept/merge Pull request #2794 Pull request review/approval and comment on code #3748 ) -
Approvals limitations (Pull requests approvals limitations #5251) -
Migrate a throughout github repository to gitea (Improve migrations to support migrating milestones/labels/issues/comments/pullrequests #6290, Proposal: Store original author in database for use with migrated content #7293, Move migrating repository from frontend to backend #6200, Change ownership of issues/comments/PR from Github user to Gitea user after migration #7410) -
Dump/restore github/gitlab repository data to a local directory and restore to gitea Dump github/gitlab/gitea repository data to a local directory and restore to gitea #12244
Migrating Progress Updated:
- migrate gitea repository -> https://gitea.com/gitea/gitea blocked by Add support to import repository data from an exported data of Github #18165
- migrate go-sdk repository -> https://gitea.com/gitea/go-sdk
- migrate git repository -> https://gitea.com/gitea/git
- migrate tea repository -> https://gitea.com/gitea/tea
- migrate website repository -> https://gitea.com/gitea/website
- migrate blog repository -> https://gitea.com/gitea/blog
- migrate theme repository -> https://gitea.com/gitea/theme
- migrate redirects repository -> https://gitea.com/gitea/redirects
- migrate homebrew-gitea repository -> https://gitea.com/gitea/homebrew-gitea
Reacted by Bo-Yi Wu, Lourens-Rich, Felix Palmgren, Andrew, Simon, Patrick Gaskin, Fabian Zaremba, Tsvetan, Alexander Feller, Kim "BKC" Carlbäcker and 155 more
Reacted by Maxime Franck, Bo-Yi Wu, Simon, Bishwa Subedi, Patrick Gaskin, Thomas, Thomas Maurice, Jorrit Klein Bramel, JC Grünhage, Darkspirit and 53 more
Reacted by silverwind and Sandro
Reacted by Lourens-Rich, Simon, Patrick Gaskin, Bo-Yi Wu, Davydov Viacheslav, Thomas, Thomas Maurice, Jorrit Klein Bramel, Claes Wallin (韋嘉誠), JC Grünhage and 56 more
Metadata
Metadata
Assignees
Labels
topic/deploymenttype/proposalThe new feature has not been accepted yet but needs to be discussed first.The new feature has not been accepted yet but needs to be discussed first.
Activity
Lourens-Rich commentedon Feb 23, 2017
Very good idea!
bkcsoft commentedon Feb 27, 2017
1.2 in February, 1.3 in April, 1.4 in June, 1.5 in August? should be enough time to implement all that 😄
zellyn commentedon Mar 10, 2017
If you haven't seen it, fantastic and insightful comment supporting your approach to self-hosting only when ready: https://lobste.rs/s/gokjbo/gitea_1_1_0_released/comments/dg9pwe#c_dg9pwe
bkcsoft commentedon Apr 7, 2017
@lunny Now that I think about it (thanks @zellyn for that link 😂 ) Why do we need oauth-provider, complete webhook support, api-documentation, and a complete API for self-hosting?
OAuth Consumer is required (it's merged AFAIK) so people can login using github auth.
Drone only uses push hooks, so why would we need the other?
As for API, not sure why self-hosting requires that at all TBH :)
strk commentedon Apr 7, 2017
I agree about trimming that list. Earlier self-hosting will very likely help us setting priorities better :)
lunny commentedon Apr 7, 2017
@bkcsoft maybe we can setup a hosted site and have a try.
lunny commentedon Apr 7, 2017
@bkcsoft I updated the issue, do you mean that?
ekozan commentedon Aug 31, 2017
-> OAuth provider (#27) is not closed
bkcsoft commentedon Aug 31, 2017
@ekozan not closed, but scratched from the list of "things we need"
bkcsoft commentedon Sep 14, 2017
Added "Repository Size Limits" since we don't have unlimited storage on the servers...
My proposal for limits:
lunny commentedon Sep 14, 2017
@bkcsoft Did you mean it will be a public service for anyone?
bkcsoft commentedon Sep 14, 2017
Maybe, maybe not, but if it becomes a public service we can't have it unlimited ;)
stevegt commentedon May 5, 2018
I think dogfooding is important enough that repo size limits may not need to be in the critical path for self-hosting gitea. In the first few days after migrating to gitea, I've run across several feature omissions that made me think self-hosting will help focus effort on getting those things done. Gitea is already a fantastic, highly usable, high-performance tool -- it's a real shame you aren't using it yourselves. ;-)
Rather than depend on hard size limits, it might instead be helpful to think about how the self-hosted server is going to be administered, who's going to police bad behavior, and what tools they will want. For instance, contributor forks of the gitea project ought to be supported on gitea's own server. This exposes the risk that a user forks gitea, then pushes warez to their fork. Size limits might help prevent pushing large binaries, but might not help with a list of passwords or credit card numbers. A tool that might help in that case is something that detects alien files by diff line count or rolling hash.
A nice side-effect of having a diff-size tool available is that the code could be available as an option to run during pushes to flag legitimate commits that should have been broken up into smaller pieces anyway. (Related discussion for ways to do this: #3658 (comment).)
I'd bet there are a lot of other subtle things that will need to be addressed for public-facing servers. It might make sense to use a separate "public hosting" master issue or milestone to track these things.
113 remaining items
techknowlogick commentedon Mar 20, 2023
There haven't been many updates on this posted, but I just wanted to say it is being worked on. The alternative export API that Github provides is sadly not working for us, it always returns that it fails to export the data. My guess is that the amount of data we have is too much. If anyone has any contacts at Github who can help us out, please let me know :) My contact email is in my bio.