Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
    • Switch to GitLab Next
  • Sign in / Register
Antora
Antora
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
    • Locked Files
  • Issues 172
    • Issues 172
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
    • Iterations
  • Merge Requests 35
    • Merge Requests 35
  • Requirements
    • Requirements
    • List
  • CI / CD
    • CI / CD
    • Pipelines
    • Jobs
    • Schedules
    • Test Cases
  • Security & Compliance
    • Security & Compliance
    • Dependency List
    • License Compliance
  • Operations
    • Operations
    • Incidents
    • Environments
  • Analytics
    • Analytics
    • CI / CD
    • Code Review
    • Insights
    • Issue
    • Repository
    • Value Stream
  • Snippets
    • Snippets
  • Members
    • Members
  • Collapse sidebar
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
  • Antora
  • AntoraAntora
  • Issues
  • #82

Closed
Open
Opened Dec 21, 2017 by Dan Allen@mojavelinuxOwner

Add option to playbook to skip worktree(s)

Writers will likely expect files in the working directory (i.e., worktree) to be picked up automatically if the content source points to a directory on the local filesystem. However, there are use cases when the writer will need to run the site only using files committed to the branch. We don't want to force writers to have to stash local changes in this case. Therefore, we should offer a playbook option to disable the worktree. We may need this both globally and per source.

The CLI switch to ignore worktrees globally should be named --skip-worktree. (I choose this name since it matches a switch in git that offers similar functionality).

This option can also be set on the content key in the playbook spec:

content:
  skip_worktree: true

or per source:

content:
  sources:
  - url: .
    skip_worktree: true

(We could also consider inverting the switch, so it's worktree: false instead of skip_worktree: true).

To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Assignee
Assign to
TBD
Milestone
TBD
Assign milestone
Time tracking
None
Due date
None
Reference: antora/antora#82