-
-
Notifications
You must be signed in to change notification settings - Fork 5.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
//feature request\\ learn gitlab ui and functions #11299
Comments
I mean what's the point? Gitea imitates Github UI which is satisfying to many users that know it. Why would it have to change? And, why is Gitlab UI better that Gitea or Github?! It's simply different, but, which one is better, is subjective for each individual. I don't disagree with the CI/CD idea but it's a really big feature, like building another platform on top. Plus it will inevitably make Gitea heavier, when running builds. Also what about ARM? ARM won't be able to have CI capabilities. Also, if I hosted a CI platform I would want it to be in a separate container at least. |
I disagree with "update project gui"! I love Gitea's simplicity. It's eye-candy in its own way :) I do like showing projects on the front-page though. It's always nice to have some UI feedback, thanks for posting. |
The default front page is already a setting (LANDING_PAGE). If you want to display repositories you can use that option to display the explore page. |
Closing as a dupe of #5937 A couple of notes about above: We do have oauth login capabilities with many other platforms including the ones you've listed above. Also in terms of CI, we integrate with many different CI providers already, and if you are looking for one like Gitlab CI, then Drone offers a similar experience and can translate existing gitlabci yaml files (perhaps others do too, but I'm listing drone here as it is the CI that I am most familiar with). For future suggestions I recommend being more detailed instead of just "Update project GUI" and providing a screenshot of gitlab, concrete & actionable steps are preferred as then everyone is on same page with what completion of ticket is. |
Nothing
The text was updated successfully, but these errors were encountered: