Update GitLab Features authored by Slominski, Ryan's avatar Slominski, Ryan
...@@ -42,6 +42,7 @@ Other items that we may not care about at the moment, but aren't available in Fr ...@@ -42,6 +42,7 @@ Other items that we may not care about at the moment, but aren't available in Fr
# Annoyances # Annoyances
- You can't remove the `+ Configure Integrations` link on the right side of every project page. This is constantly prompting users to add an integration, even if we really would prefer not to be constantly prompting users to do so. Most of the integrations appear to be Admin-level tasks to setup and require auth tokens for example. Just confusing noise for regular users (devs). - You can't remove the `+ Configure Integrations` link on the right side of every project page. This is constantly prompting users to add an integration, even if we really would prefer not to be constantly prompting users to do so. Most of the integrations appear to be Admin-level tasks to setup and require auth tokens for example. Just confusing noise for regular users (devs).
- When copy and pasting URLs you'll notice most contain `?ref_type=heads`. This is just annoying and is described here: https://gitlab.com/gitlab-org/gitlab/-/issues/424908 - When copy and pasting URLs you'll notice most contain `?ref_type=heads`. This is just annoying and is described here: https://gitlab.com/gitlab-org/gitlab/-/issues/424908
- When you create a new Project with the new Project button on the web page, users are prompted to check a box to add Secret Detection and/or Security Testing. Neither actually work if you select them. Confusion ensues. For one, it attempts to modify the CI/CD pipeline with a template (which is deprecated in favor of CI/CD Components), and it doesn't work anyways. Plus, you need Ultimate Edition to actually prevent commit of secrets, which is what you really want. Once already committed, you'd then have to scrub and then change the secret.
# Usage Tip: Avatars / Images # Usage Tip: Avatars / Images
In GitLab, Projects, Users, and Groups can all be configured with avatars (a profile image). A good source of these is Emoji's that have been converted to images since these have fewer distribution restrictions, plus you can then generally easily maintain your project branding in Markdown files using GitLab's built-in emoji's. In particular, Microsoft provides SVG images of most Emoji's here: [Fluent Emoji](https://github.com/microsoft/fluentui-emoji). The images are under the `assets` directory and generally you'll want the color versions. There are so many subdirectories that GitHub web interface won't list them all, so you'll have to use the search box to access anything at the end if the alphabet. You'll also need to convert them to PNG of size 192x192 pixels, which can be done via various online converters. In GitLab, Projects, Users, and Groups can all be configured with avatars (a profile image). A good source of these is Emoji's that have been converted to images since these have fewer distribution restrictions, plus you can then generally easily maintain your project branding in Markdown files using GitLab's built-in emoji's. In particular, Microsoft provides SVG images of most Emoji's here: [Fluent Emoji](https://github.com/microsoft/fluentui-emoji). The images are under the `assets` directory and generally you'll want the color versions. There are so many subdirectories that GitHub web interface won't list them all, so you'll have to use the search box to access anything at the end if the alphabet. You'll also need to convert them to PNG of size 192x192 pixels, which can be done via various online converters.