Live data from Hacker News

GitLab 10.6 released with CI/CD for GitHub

about.gitlab.com

101–107 of 107 posts

Re: GitLab 10.6 released with CI/CD for GitHub

#101
post #25

Earlier quoted context omitted.

At least you can blame previous revisions of a file? Using an URL like gitlab.com/username/project/blame/COMMITHASH_OR_TAG/path/to/file

You can, but you need to copy-paste the hash to the URL manually, which is not exactly good UX.

No you don't? If you click on a particular commit, you can click "View file @ HASH" and from the click the Blame button?

Re: GitLab 10.6 released with CI/CD for GitHub

#102
post #45

Earlier quoted context omitted.

Ive got mixed feelings about yaml as well, but which format would you prefer? The Jenkins DSL ist terrible to debug and XML is way too verbose for such a usecase. Yaml is honestly the best option here.

TOML is much better.

i don't know any CI/CD framework which utilizes it though.

and i'm unsure if it really is. There are some imo really good features missing such as document separation, cross references and the newline to space conversion.

toml would be great for pretty much everything thats under /etc/ though.

Re: GitLab 10.6 released with CI/CD for GitHub

#103
post #101

Earlier quoted context omitted.

You can, but you need to copy-paste the hash to the URL manually, which is not exactly good UX.

No you don't? If you click on a particular commit, you can click "View file @ HASH" and from the click the Blame button?

When you click on a particular commit, you see all the files affected by that commit, which can be in the dozens. Now you have to search for the file you're interested in again, click on View file at..., then in there search again for the line you're interested in, click on it then go back to the top of the page and click on Blame (or click Blame first and search for your line later, same thing).

How many steps was that?

Re: GitLab 10.6 released with CI/CD for GitHub

#104

I hate it that Gitlab is focusing too much on all these project-management features, while neglecting the basic code review features such as commenting on a block of code, or making a review session instead of creating individual comments, or the ability to blame previous revisions of a file

These are exactly the type of features we are focused on this year. Commenting on a block of code: https://gitlab.com/gitlab-org/gitlab-ce/issues/4143 Making a review session: https://gitlab.com/groups/gitlab-org/-/epics/23 And here’s a greater overview: https://about.gitlab.com/direction/#merge-requests-approvals...

Now if you guys would get to...

1. ... allow to specify somehow a size of TAB symbol per user or per project (or per review), so we might be able to review Go code normally, without plugins or custom CSS for the browser (8 char default is making code a lot harder to review,especially side-by-side). Yes, there were at least 3 different tickets opened about it the last time I have checked. No, the answer "we going to have .editorconfig support one day" or "good suggestion, maybe one day" are not making it after 2+ years, sorry)

2. ... filename not being hidden by icons would be so awesome in knowing which Java file with 200 char filepath I am trying to review without copying filename to clipboard, and looking at it in VS Code. Wrapping icons is ok, I don't care where is "copy file name" button is located that much.

3. ... have some file patterns rules about what files I would like to have collapsed by default. And while we are at it, add what files to display with ignore-space diff, and which do not, so I will not start every review with the same magic mouse triple click with full reloads of 15 files in between.

Sorry for the rant, code reviews is one of my main responsibilities and this just drives me nuts every day.

Re: GitLab 10.6 released with CI/CD for GitHub

#105

I really want to try GitLab, but I can't log in to their service with oAuth using Google as a provider. I get a 422. I brought this up with GitLab's support, and they essentially told me it was my fault and doing something wrong with JS or something. It's just me clicking on links on their page, wtf. The interaction with their support was enough to turn me away from their service if that's the type of help they provi…

I ran into this recently. You probably created a GitLab account with your Gmail address first and then afterwards tried logging in with OAuth and encountered the 422. Try logging in without OAuth, then enable social sign in under https://gitlab.com/profile/account

Unfortunately, it's not the same problem. I get the same results from multiple gmail/gsuite addresses. womp womp

Re: GitLab 10.6 released with CI/CD for GitHub

#106
post #32

I really want to try GitLab, but I can't log in to their service with oAuth using Google as a provider. I get a 422. I brought this up with GitLab's support, and they essentially told me it was my fault and doing something wrong with JS or something. It's just me clicking on links on their page, wtf. The interaction with their support was enough to turn me away from their service if that's the type of help they provi…

Please email me directly. (email in profile) I'd like to look into what happened here.

I sent you an email.
Post reply on HN