Skip to content

GitLab

  • Menu
Projects Groups Snippets
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • F format-source
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 6
    • Issues 6
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 1
    • Merge requests 1
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Packages & Registries
    • Packages & Registries
    • Container Registry
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • mercurial
  • format-source
  • Issues
  • #3

Closed
Open
Created Dec 30, 2018 by Georges Racinet@gracinet🦑Owner

detect mode configuration issue and warn about them

Created originally on Bitbucket by marmoute (Pierre-Yves David)

A common error mode, is to have a tool configured as "pipe" output while actually performing an inplace update.

Currently, the formatter runs fine, and format source read an empty file. Since is pretty bad the merge mechanism will see an empty "base" and "other", picking "local" as is.

I'm pretty sure there is not formatting tools that will return "Nothing" when passed something. So we can detect this to detect the error and warn the user about it.

To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Assignee
Assign to
Time tracking