3 ms·
You've gotta look at it this way - when github updates do I even notice? Have you ever had a bug that stopped you working on github? I personally use github all
by yarper 11y ago
You've gotta look at it this way - when github updates do I even notice? Have you ever had a bug that stopped you working on github? I personally use github all the time and have never seen a bug on it. I trust it completely (well.. tech wise).
Our repository is a few million lines, maybe 20,000 commits. The search works fine now it has been changed to call out to git properly (aside from the js searchbox thing in ff). Repositories are stored on the same server. I'm not going to dig up all the issue numbers and turn this into a support request, I am involved in reporting these and commenting on them @ gitlab.com.
The syntax highlighting updates have been very well received, but I mean gitlab was shipped with syntax highlighting that doesn't work properly with Java code. Not exactly a unusual lang. And I guess that's where my rant was going - you can't ship crap like that, you should be shipping with 0 known bugs. Every time gitlab ships a bug like this, I take a knock in the office on your behalf and that's why I'm so openly annoyed.
Perhaps you could do a LTR or open a beta programme for early adopters?
- sytse 11y agoI'm glad to hear most things are working now. We're hiring to put more eyes on the open issues on GitLab.com. If you want a more stable GitLab upgrade to a new minor release on the 21th of every month. At that time all the patches should have landed. We strive to fix all known regressions. If they want to use the bleeding edge people can use our release candidates. Or run master, like we do on our internal server.