GitLab 8.9 released
about.gitlab.com
GitLab 8.9 released
1–10 of 63 posts
Re: GitLab 8.9 released
#2merge restriction as a feature may sound silly, but in my experience, when driving organizations toward CI/CD, especially with "mature" organizations, having the computer say no instead of a human is a major facilitator in adoption of good practices. now we just need to protect tests in tree. (currently, i tend to favor tests as a git submodule, so we can prevent chronic offenders from altering/commenting tests that should pass)
plus U2F integration, so now i won't hear anymore how "terribly slow" it is to have to whip out a phone to grab a TOTP code...
Re: GitLab 8.9 released
#3gitlab is gearing up to be the one-stop-shop from development to production. i really like that. unifying the toolset developers and ops have to understand is really a boon for everybody involved. merge restriction as a feature may sound silly, but in my experience, when driving organizations toward CI/CD, especially with "mature" organizations, having the computer say no instead of a human is a major facilitator in…
Are you using that seriously already?
Re: GitLab 8.9 released
#4Re: GitLab 8.9 released
#5gitlab is gearing up to be the one-stop-shop from development to production. i really like that. unifying the toolset developers and ops have to understand is really a boon for everybody involved. merge restriction as a feature may sound silly, but in my experience, when driving organizations toward CI/CD, especially with "mature" organizations, having the computer say no instead of a human is a major facilitator in…
Re: GitLab 8.9 released
#6Will repo deploy tokens ever be a thing? I would like read-only deploy tokens associated to a repo, and not a user. I just don't like having to create dummy users with repo access to generate deploy tokens.
Re: GitLab 8.9 released
#7Will repo deploy tokens ever be a thing? I would like read-only deploy tokens associated to a repo, and not a user. I just don't like having to create dummy users with repo access to generate deploy tokens.
Deploy keys give read-only access to clone a repository, and they are associated directly with the repository.
Re: GitLab 8.9 released
#8Re: GitLab 8.9 released
#9gitlab is gearing up to be the one-stop-shop from development to production. i really like that. unifying the toolset developers and ops have to understand is really a boon for everybody involved. merge restriction as a feature may sound silly, but in my experience, when driving organizations toward CI/CD, especially with "mature" organizations, having the computer say no instead of a human is a major facilitator in…
I don't know if this applies to you, but 1Password 6 has support for generating TOTP passwords (they have a neato QR scanner built in, or one can always just input the key or key URI by hand)
It's been a revolutionary change in my day-to-day frustration level
Re: GitLab 8.9 released
#10Keep up the good work.