If there are ways we can improve how we engage with the HN community, myself and our team would love your feedback.
991 karma · joined March 1, 2015
If there are ways we can improve how we engage with the HN community, myself and our team would love your feedback.
Comment (and code) search is available for projects in all GitLab tiers: https://docs.gitlab.com/ee/user/search/#basic-search
Premium and Ultimate users have access to Advanced Search: https://docs.gitlab.com/ee/user/search/advanced_search.html
I'm on the Community Relations team at GitLab. I'd love to learn more about your experience as a member of the GitLab community.
When you say that opening an issue on GitLab doesn't make you feel part of a community, are you referring issues on one of GitLab's projects (ex: https://gitlab.com/gitlab-org/gitlab) or are you referring to issues on open source projects being hosted on GitLab.com?
Community is very important to us so when there are areas for improvement that feedback is really valued.
Please see this post on the GitLab forum for details how you can determine if your instance has been compromised through the exploitation of CVE-2021-22205: https://forum.gitlab.com/t/cve-2021-22205-how-to-determine-i...
The way to keep up-to-date on critical security updates for GitLab is to sign up for our Security Alerts mailing list: https://about.gitlab.com/company/preference-center/
Due to a security concern in which a profile containing a file extension would not load [3], we do not allow usernames that end with file extensions (ex: .mov). As noted by many folks here, these are associated with a MIME type but are not MIME types themselves. It is not related to preventing an injection or any such attack vector.
The error message for this check incorrectly included MIME type rather than file extension. This has been updated [4].
Additionally, there was an issue with how the actual check as it did not include the leading dot. The leading dot was added to the check in a subsequent MR [5].
Thanks for all the feedback.
1 - https://news.ycombinator.com/item?id=28535739
2 - https://news.ycombinator.com/item?id=28538166
3 - https://gitlab.com/gitlab-org/gitlab/-/issues/26295
4 - https://gitlab.com/gitlab-org/gitlab/-/merge_requests/70374/...
5 - https://gitlab.com/gitlab-org/gitlab/-/merge_requests/65954
- keep good magazines laying around places where you would normally reach for your phone (near the couch, desk, bed, and let's be honest the bathroom)
- play a musical instrument
- walk my dog
- slow transportation (traveling by foot or bicycle)
- surfing and basketball
We've put a lot of effort into our integration with Jira. The docs [1] detail how it works and we have a blog [2] with some screenshots so you can see what it looks like in action.
What kind of troubles have you encountered?
1 - https://docs.gitlab.com/ee/integration/jira/
2 - https://about.gitlab.com/blog/2021/03/25/integrating-gitlab-...
Git is a trademark of Software Freedom Conservancy and our use of 'GitLab' is under license.
Can you share a bit more about the issues you are having? Would be happy to try to help resolve or open an issue if its a bug.
This tweet from GitLab's CEO provides some additional context: https://twitter.com/sytses/status/1417617071353991169?s=19
Team members who meet the requirements follow our relocation process which is managed by People Operations Specialists.
Team members who do not meet all of the requirements are asked to work with their managers first before bringing the request to the People team.