gitlab-org--gitlab-foss/app/assets/stylesheets/application.scss
Lukas Eipert 7d00eea697
Use absolute paths for SCSS imports
A recent update in [GitLab UI] and setting the [config.assets.paths] to
include `node_modules` for the resolution of SCSS imports, allows us to
have much nicer imports which don't rely on brittle relative paths.

This change also forwards @gitlab/ui to the newest version

[GitLab UI]: https://gitlab.com/gitlab-org/gitlab-ui/merge_requests/602
[config.assets.paths]: https://gitlab.com/gitlab-org/gitlab-ce/blob/d9026d0ffa0/config/application.rb#L169
2019-06-28 18:47:00 +02:00

37 lines
1.1 KiB
SCSS

/*
* This is a manifest file that'll automatically include all the stylesheets available in this directory
* and any sub-directories. You're free to add application-wide styles to this file and they'll appear at
* the top of the compiled file, but it's generally better to create a new file per style scope.
*= require_self
*= require cropper.css
*/
// Welcome to GitLab css!
// If you need to add or modify UI component that is common for many pages
// like a table or typography then make changes in the framework/ directory.
// If you need to add unique style that should affect only one page - use pages/
// directory.
@import "at.js/dist/css/jquery.atwho";
@import "pikaday/scss/pikaday";
@import "dropzone/dist/basic";
@import "select2/select2";
// GitLab UI framework
@import "framework";
// Font icons
@import "font-awesome";
// Page specific styles (issues, projects etc):
@import "pages/**/*";
// Component specific styles, will be moved to gitlab-ui
@import "components/**/*";
// Vendors specific styles
@import "vendors/**/*";
// Styles for JS behaviors.
@import "behaviors";
@import "utilities";