Be sure to let us know how we can help, and you are welcome to open issues on GitHub or join our Discord if you have questions.
487 karma · joined October 12, 2017
Be sure to let us know how we can help, and you are welcome to open issues on GitHub or join our Discord if you have questions.
For example the Spending Company Money page [2] doesn't begin and end with the quote I shared - it just begins with it. It's the starting point, and in no way the articulation of the _entire_ policy. There are lots of guidelines past that to help folks out and understand what is reasonable...but the starting point is what is important. Trusting people to make good decisions for themselves and for the company is a very healthy thing, and I feel bad for folks who haven't gotten to experience that in work environments.
Thanks for all the commentary - it was a nice send off to make it to the top of this site for a time :)
[1] https://about.gitlab.com/handbook/values/
[2] https://about.gitlab.com/handbook/spending-company-money/
Edited for spacing and to say - one last time - GitLab employee here.
The link is https://blog.boleary.dev/gitlabs-values/#disagree-commit-and...
[pull]
rebase = true
edited for line spacing
Wanted to make sure you saw this: https://twitter.com/gitlab/status/1555325376687226883
GitLab employee here.
You're correct. We also have Redis for a few things: Rails caching, Sidekiq jobs, session data, CI, and a few other things. You can learn more about GitLab.com's infrastructure architecture here [1] and more about what Redis is used for here [2].
[1]: https://about.gitlab.com/handbook/engineering/infrastructure... [2]: https://docs.gitlab.com/ee/development/redis.html
We did experiment with a few ideas outside of this decomposition method. In the end what you talked about here in your comment is exactly correct. And we value boring solutions in the end: https://about.gitlab.com/handbook/values/#boring-solutions.
There is work to do, and product and engineering are putting more focus on fixing longstanding issues, and increase reliability. Specifically for GitLab Runner, 15.0 and later bring many fixes, next to supporting podman.
https://gitlab.com/groups/gitlab-org/-/issues/?sort=updated_...
- Add squash commits option in push options for merge requests [1]
- Show equivalent push options at bottom of /-/pipelines/new [2]
- Show equivalent push options at bottom of create merge request page [3]
[1]: https://gitlab.com/gitlab-org/gitlab/-/issues/324619
[2]: https://gitlab.com/gitlab-org/gitlab/-/issues/359268
[3]: https://gitlab.com/gitlab-org/gitlab/-/issues/359269
(edited for line spacing)
And thoughts on making it easier? Maybe a suggested set of git aliases or some sort of wrapper?
https://docs.gitlab.com/ee/user/admin_area/reporting/spamche...
We have internal tooling that we're working on incorporating into GitLab itself to help with this: https://about.gitlab.com/blog/2021/08/19/introducing-spamche....
> no way to combine a text search with label/milestone/status filters, etc.
You can combine text search with field search (like label/milestone/status. Here’s an example: https://gitlab.com/gitlab-org/gitlab/-/issues?search=Visuali...
We believe we have mitigated the incident, but continue the work to monitor and make additional corrective measures: https://twitter.com/gitlabstatus/status/1462838897499508737
Also don't miss that two more paid features were added to the free tier of GitLab EE as part of our Registration Features Program [4].
[1] https://about.gitlab.com/blog/2021/10/12/open-shift-ga/
[2] https://docs.gitlab.com/ee/user/project/web_ide/
[3] https://about.gitlab.com/releases/2021/10/22/gitlab-14-4-rel...
[4] https://docs.gitlab.com/ee/development/service_ping/index.ht...
Also big thanks to our MVP this month for adding a GREAT feature for opening remote repositories with the GitLab VSCode extension.
(edit for line breaks)