Skip to content
GitLab
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • B bootstrap
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 263
    • Issues 263
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 114
    • Merge requests 114
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Packages and registries
    • Packages and registries
    • Package Registry
    • Infrastructure Registry
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • Bootstrap
  • bootstrap
  • Merge requests
  • !35592

move theme-colors (vars+map) after color tints definitions

  • Review changes

  • Download
  • Email patches
  • Plain diff
Merged maks requested to merge github/fork/pine3ree/patch-5 into main Dec 23, 2021
  • Overview 5
  • Commits 1
  • Pipelines 0
  • Changes 1

In this way we can use color tints (other than grays) in our custom theme (e.g $primary: $indigo-600; ), w/o having to extend $theme-colors and redefine $theme-colors-rgblater. This could be done in the project variables file, but i believe most developers just include a full local copy of scss/_variables.scss before the the original default file and change the values the need (maybe also removing the !default flag) so that it's easier to track changes and custom values during upgrades.

Assignee
Assign to
Reviewers
Request review from
Time tracking
Source branch: github/fork/pine3ree/patch-5