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
  • !17520

Specify configBridge as relative path to source for Jekyll

  • Review changes

  • Download
  • Email patches
  • Plain diff
Merged Administrator requested to merge github/fork/davidjb/v4-dev-relative-grunt into v4-dev Sep 08, 2015
  • Overview 0
  • Commits 1
  • Pipelines 0
  • Changes 1

Created by: davidjb

This adjusts the load path for the configBridge.json file from one that's relative to where user is running the build or serve command (eg jekyll serve), to one that's relative to the source configuration setting for Jekyll.

The result is that a user can now have a _config.yml anywhere on her filesystem and point to Bootstrap's docs directory to use as Jekyll's source. Previously, customisations involved the original _config.yml needing to be modified inside (a forked) Bootstrap. Similarly, the jekyll command could only be run at the root of the Bootstrap package since the original file path to configBridge.json was only valid there; a command like jekyll serve --source path/to/bootstrap/docs (run from any directory) can succeed.

The existing behaviour is not affected as the grunt/ directory is always a sibling of docs in the current structure.

Assignee
Assign to
Reviewers
Request review from
Time tracking
Source branch: github/fork/davidjb/v4-dev-relative-grunt