Y
HN Search
Hacker News Search
new
|
comments
|
top
|
jobs
sytse
searching PlanetScale…
1.
▲
2.
▲
3.
▲
4.
▲
5.
▲
6.
▲
30 ms
·
301.
▲
by
sytse
6y ago
For people who want to compare GitHub Insights to GitLab please consider looking at GitLab Insights https://docs.gitlab.com/ee/user/project/insights/ Code Review Analytics https://docs.gitlab.
302.
▲
by
sytse
6y ago
Thanks for the mention. As for how the features today map: 1. GitHub Insights => GitLab Insights https://docs.gitlab.com/ee/user/project/insights/ Code Review Analytics https://docs.gitlab.
303.
▲
by
sytse
6y ago
Thanks! Docs for the GitLab feature to show CI results in a structured way are on https://docs.gitlab.com/ee/ci/junit_test_reports.html GitHub Codescanning functionality is best compared to what GitLab has in GitL
304.
▲
by
sytse
6y ago
Docs for this are on https://docs.gitlab.com/ee/user/project/issues/issue_data_an...
305.
▲
by
sytse
6y ago
Yep, and the default is now to both create a branch and a merge request https://www.dropbox.com/s/hgcwyifxkc6jrxh/Screenshot%202020-...
306.
▲
by
sytse
6y ago
Sorry but it is late for me and I don’t understand. In general we try to allow you to aggregate at all the group levels and help you group under epics.
307.
▲
by
sytse
6y ago
In case it helps anyone: you can turn off issues in a GitLab project if you don’t want to see them.
308.
▲
by
sytse
7y ago
Awesome!
309.
▲
by
sytse
7y ago
Even worse than SEO, fraudsters edited Google Maps bank information directly http://archive.vn/PPJYW
310.
▲
by
sytse
7y ago
Congrats on launching. It must have been a lot of work to make Redis serverless. If you feel comfortable it would be interesting to know more about the technical underpinnings.
311.
▲
by
sytse
7y ago
We don't accept inbound applications from outside the company anymore. We do have a talent community https://boards.greenhouse.io/gitlab/jobs/4700367002?gh_src=d... Thanks for planning to contribute to GitLab
312.
▲
by
sytse
7y ago
I have not seen it a clearly as you describe, but at GitLab we've seen a bit of the same. The digital nomads that move to a new room weekly tend to have a hard time focussing on work. People that move every couple of months or that hav
313.
▲
by
sytse
7y ago
These attacks will become more common. I'm advocating to add a dependency firewall to GitLab so that downloads of packages that show suspicious behaviour will be paused. I've added some of the vectors of this attack to the signals
314.
▲
Columnal
(columnal.xyz)
1 points
by
sytse
7y ago
|
0 comments
315.
▲
by
sytse
7y ago
And we quickly fixed https://gitlab.com/gitlab-org/quality/performance/-/merge_re...
316.
▲
by
sytse
7y ago
And we created https://gitlab.com/gitlab-org/gitlab/-/issues/214681
317.
▲
by
sytse
7y ago
The issue for this is at https://gitlab.com/gitlab-org/gitlab/issues/36424
318.
▲
by
sytse
7y ago
We don’t know exactly how many people use it since it is open source but I think between 100,000 and 1 million people. The docker container registry is the most popular. The security curation examples I mentioned are intended to use automat
319.
▲
by
sytse
7y ago
Me too. If someone has data on predictors of compromised packages I’m all ears.
320.
▲
by
sytse
7y ago
I think hosting a package repo will generally create more downloads (costs money) than uploads (helps with peering but costs storage) because the average number of downloads for a package is more than 1.
321.
▲
by
sytse
7y ago
Yep, non-canonical registries are used by business and they are more likely to pay. For example our dependency firewall will be a paid feature that delays updates from packages that are recently updated under suspicious circumstances like:
322.
▲
by
sytse
7y ago
Someone asked "Would this have made sense for a company like GitLab if they didn't have the corporate backing of something like MS?" and deleted their comment while I was writing the answer below: Being the canonical registry
323.
▲
by
sytse
7y ago
I totally agree. The word eliminated is surprisingly common in the US but I think it has violent connotations. Alternatives are harder than I thought but separating, off-boarding, and reduction in force (RIF) might help depending on the con
324.
▲
by
sytse
7y ago
Thanks, I agree we should focus more on loading speed and we'll do so in our second fiscal quarter that starts in two weeks https://about.gitlab.com/company/okrs/fy21-q2/ The comment you linked says: &qu
325.
▲
by
sytse
7y ago
I agree, thanks for the numbers. I'll suggest to incorporate this into our Q2 OKRs. For our references please see https://storage.googleapis.com/sitespeed-results-gitlab/gitl... and https://about.gitlab
326.
▲
by
sytse
7y ago
That is a great suggestion. GitLab has burn-down charts https://docs.gitlab.com/ee/user/project/milestones/burndown_... that show that progress isn't linear. What is small change we can make to stre
327.
▲
by
sytse
7y ago
Just making sure that you are aware that GitLab supports sizing and estimations via weights https://docs.gitlab.com/ee/user/project/issues/issue_weight....
328.
▲
by
sytse
7y ago
I was doing iteration office hours https://www.youtube.com/watch?v=u5e-6R5NWl0 :)
329.
▲
by
sytse
7y ago
For self-hosted instances you can use Advanced Global Search https://docs.gitlab.com/ee/user/search/advanced_global_searc... to do this. Please note that this requires installation of Elastic Search. It used
330.
▲
by
sytse
7y ago
I think time tracking in GitLab originated as a way to track time if you're working for multiple clients, but I'm not sure.
More ›