Hacker Newsnew | past | comments | ask | show | jobs | submit | haynes's commentslogin

In that case https://githost.io/ might be interesting for you. private managed instance of gitlab.


almost, yes. issues, wiki, PRs and comments are imported. Afaik cross repo PRs are not supported yet. But they're working on that. :)


For sure, progress on that is in https://gitlab.com/gitlab-org/gitlab-ce/issues/15528

(BTW labels are also imported)


Actually you can add priorities to labels :) http://docs.gitlab.com/ce/user/project/labels.html#prioritiz... You can also search for several labels in the current release. Just select some in the dropdown :)


How has your experience of installing gitlab on freebsd been? Anything in particular that can be improved? I'm pretty sure the gitlab team is open for all kind of improvements. :)


Someone wrote a very nice and detailed guide, however upgrading isn't mentioned[0]

it also suggests operating under bad practices like running gitlab from /home/

I guess I could write a decent salt-formula to do all this, but I can't handle upgrading of gitlab easily, it always breaks when I take a new branch from git and run a gitlab-ctl reconfigure.

[0]: https://github.com/gitlabhq/gitlab-recipes/blob/master/insta...



Indeed. The search field is currently only displayed for users that have logged in.


Thanks, that doesn't make sense so I made an issue to remedy it https://gitlab.com/gitlab-org/gitlab-ce/issues/13676


Update: we'll ship this fix with 8.6. It has just been merged.


Great!


Your account on gitlab.com is completly free and permanent unless you decide to delete it yourself.

The 45 day trial is for the case when you want to host gitlab-ee yourself on your own server.


Importing Pull Requests will be possible with the next version of gitlab that's going to be released on the 22nd january. See this MR for more information: https://gitlab.com/gitlab-org/gitlab-ce/merge_requests/2168


That's a bug in the website.

The correct and active account is @gitlabstatus


Indeed, we'll update the status page to reflect this https://gitlab.com/gitlab-org/status-gitlab-com/commit/1d4cf...


Ahh I know where that came from. The runners push the build results back to the coordinator (which is now included in gitlab). So in theory, if you have a large number of runners and a very large number of concurrent builds, it could slow down gitlab a little bit. But the numbers you need to reach this are pretty high.


Hi guelo,

can you elaborate a bit more what you are looking for? What kind of structure do you need?

Without these informations, I'll just throw gitlab in the possible alternatives pool.

https://about.gitlab.com/features/

Please note that I'm biased since I'm on the gitlab core team. :)


Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: