Download Gitlab Icon

It's odd -- contrary to what @sytech posted, I've noticed that I sometimes have multiple tabs open to the same GitLab page (e.g. an open MR) and one of them has the orange icon and the other has the yellow one. For example, right now:

yeah, I just looked at the inspector in Firefox too, and I don7t see anything in the head that loads the font awesome library. I see an icon with some small characters in it, but, not the bars icon that this is calling:

Download File 🔥 https://bltlly.com/2y3B7d 🔥

This open source icon is named "Gitlab" and is licensed under the open source CC0 license. It's available to be downloaded in SVG and PNG formats (available in 256, 512, 1024 and 2048 PNG sizes).

It's part of the icon set "SVG Logos", which has 1,190 icons in it.

This graphic is also a logo. It's useful if you want to show the logo (for branding purposes) on your website or app.

If you need this icon available in another format, it should be pretty straight forward to download it as an SVG image file, and then import it into apps like Adobe Illustrator, Crello, Figma or RelayThat. Converting it to an ICO, JPEG or WebP image format or file type should also be pretty simple (we hope to add that feature to Iconduck soon).

This icon can be used for both Personal & Commercial purposes and projects, but please check the license to see if the designer is requesting attribution (for example, a link back to their website).

Yes! This icon has been open sourced, and can be downloaded at no charge / for free. We also don't require you to sign up for Iconduck, but you can join our mailing list to get notifications on when new icons are available.

Several options are available for customizing the appearance of a self-managed instanceof GitLab. To access these settings:On the left sidebar, at the bottom, select Admin Area.Select Settings > Appearance.Navigation barBy default, the navigation bar has the GitLab logo, but this can be customized withany image desired. It is optimized for images 28px high (any width), but any image can beused (less than 1 MB) and it is automatically resized.After you select and upload an image, select Update appearance settings at the bottomof the page to activate it in the GitLab instance.noteGitLab pipeline emails also display the custom logo, unless the logo is in SVG format. If thecustom logo is in SVG format, the default logo is used instead because the SVG format is notsupported by many email clients.FaviconBy default, the favicon (used by the browser as the tab icon and the CI status icon)uses the GitLab logo. This can be customized with any icon desired. It must be a32x32 .png or .ico image.After you select and upload an icon, select Update appearance settings at the bottomof the page to activate it in the GitLab instance.System header and footer messagesEnable header and footer in emails checkbox introduced in GitLab 15.9.You can add a small header message, a small footer message, or both, to the interfaceof your GitLab instance. These messages appear on all projects and pages of theinstance, including the sign-in/sign-up page. The default color is white text onan orange background, but this can be customized by selecting Customize colors.Limited Markdown is supported, such as bold, italics, and links, forexample. Other Markdown features, including lists, images, and quotes are not supportedas the header and footer messages can only be a single line.You can select Enable header and footer in emails to have the text ofthe header and footer added to all emails sent by the GitLab instance.After you add a message, select Update appearance settings at the bottom of the pageto activate it in the GitLab instance.Sign-in / Sign-up pagesYou can replace the default message on the sign-in/sign-up page with your own messageand logo. You can make full use of Markdown in the description.The optimal size for the logo is 128 x 128 pixels, but any image can be used (below 1 MB)and it is resized automatically. The logo image appears between the title andthe description, on the left of the sign-up page.After you add a message, select Update appearance settings at the bottom of the pageto activate it in the GitLab instance. You can also select Sign-in page,to review the saved appearance settings:noteYou can add also add a customized help message below the sign-in message or add a Sign-in text message.Progressive Web AppIntroduced in GitLab 15.9.GitLab can be installed as a Progressive Web App (PWA).Use the Progressive Web App settings to customize its appearance, including its name,description, and icon.Configure the PWA settingsTo configure the PWA settings:On the left sidebar, at the bottom, select Admin Area.Select Settings > Appearance.Scroll to the Progressive Web App (PWA) section.Complete the fields.Icon: If you use the standard GitLab icon, it is available in sizes 192x192 pixels,512x512 pixels, also as a maskable icon. If you use a custom icon, it must be in either size192x192 pixels, or 512x512 pixels.Select Update appearance settings.New project pagesYou can add a new project guidelines message to the New project page in GitLab.You can make full use of Markdown in the description:The message is displayed below the New Project message, on the left sideof the New project page.After you add a message, select Update appearance settings at the bottom of the pageto activate it in the GitLab instance. You can also select New project page,which brings you to the new project page so you can review the change.LibravatarLibravatar is supported by GitLab for avatar images, but you mustmanually enable Libravatar support on the GitLab instance to use the service.

The icons in the classic style are found in the marvosym package, whereas the other styles use fontawesome for the icons. Marvosym does not have a Gitlab icon, so if you want this icon in the classic style then you need to load fontawesome and define the icon command for moderncv.

There are four icon collections used in the product (not including the Web IDE): UI, status, pipeline, file and folder icons. The design guidelines covered in the sections below only apply to UI and status icons.

As the largest of the four collections, comprising of several subcategories, these icons are used broadly in the product to represent GitLab concepts and indicate actions and information in the UI. UI icons can be interactive or informational depending on the context. Third-party brand icons are included in this collection, but are exempt from most design guidelines.

These icons represent the status of a pipeline, like running and pending. There are both bordered and borderless versions of each icon. They use a separate grid from all other icons and are also used to generate favicons associated with web pages. Although a pipeline status can overlap conceptually with status elsewhere in the product, these icons are strictly limited to the pipeline context.

These third-party icons have specific file and language associations, like SCSS, JavaScript, and YAML, and are maintained under a separate MIT license. More information can be found in the project repository.

The 16px icon size is the default, and most UI icons are created at this size. Icons using this 1616 pixel grid have a 14px live area surrounded on all sides by 1px for padding and optical sizing.

The 12px grid is used for all status icons, and some UI icons. Icons using this 1212 pixel grid have a 10px live area surrounded on all sides by 1px for padding and optical sizing.

A keyline grid is a set of guides to help maintain optical balance (visual weight) between icons. Use it as a starting point and guide, but not a hard rule. There are four basic shapes that represent common icon scale and placement. Squares can fill the live area, while circles and rectangles can extend into the padding, which allows icons to be proportionately consistent.

In regard to icons, optical balance is the perceived size of an icon relative to other icons. The more that icons feel balanced with one another, the easier it will be to rely on other characteristics to provide visual hierarchy and flow in the UI. Icons that are not balanced can draw unnecessary attention to themselves, or seemingly disappear in the mix of other elements.

Nearly all UI icons use a 1.5px stroke weight. Lines use rounded caps, unless doing so would misrepresent the metaphor, or if you are trying to infer depth or element clipping. Round line joins are optional and also depend on the metaphor. For example, a checkmark is one continuous object and the round line infers fluidity, whereas clock hands are two joined objects and a miter join defines a joint.

Using a stroke (outline) is the default design approach, however a limited number of UI icons and all status icons use a solid fill instead. As a general rule, UI icons that use a solid fill have a specific reason for doing so. For example, the clear () icon used to clear a text input requires extra visual weight to not be missed in the UI, and thus has a solid fill applied.

Use increments of 15 to achieve consistency throughout the icon set. Angles can be combined in an icon to create more dynamic shapes and movement, while remaining consistent as a whole.

In another more literal example, an icon representing tabular data should have crisp edges. Why? Because the UI of tables in the product have crisp, 90 angles. This creates a 1:1 relationship between the icon and the object it represents, making it much easier for users to infer the intended meaning. 2351a5e196