sds/overcommit · error · Overcommit::Exceptions::ConfigurationSignatureChanged

Signature of configuration file has changed! Run `overcommit

Error message

Signature of configuration file has changed!
Run `overcommit --sign` once you've verified the configuration changes.

What it means

Error "Signature of configuration file has changed! Run `overcommit --sign` once you've verified the configuration changes." thrown in sds/overcommit.

Source

Thrown at lib/overcommit/configuration_loader.rb:99

      config
    rescue Overcommit::Exceptions::ConfigurationSignatureChanged
      raise
    rescue StandardError => e
      raise Overcommit::Exceptions::ConfigurationError,
            "Unable to load configuration from '#{file}': #{e}",
            e.backtrace
    end

    private

    def verify_signatures(config)
      if !config.previous_signature?
        raise Overcommit::Exceptions::ConfigurationSignatureChanged,
              "No previously recorded signature for configuration file.\n" \
              'Run `overcommit --sign` if you trust the hooks in this repository.'

      elsif config.signature_changed?
        raise Overcommit::Exceptions::ConfigurationSignatureChanged,
              "Signature of configuration file has changed!\n" \
              "Run `overcommit --sign` once you've verified the configuration changes."
      end
    end
  end
end

View on GitHub (pinned to fee0cd74b2)

Solutions

1. Review the diff of the changed Overcommit configuration, verify the changes are safe, then run `overcommit --sign` to accept the new signature.
2. If the change was unexpected, revert the configuration file to the previously signed version.

When it happens

Trigger: Thrown at lib/overcommit/configuration_loader.rb:99 when the library encounters an invalid state.

Common situations: See trigger scenarios.

AI-assisted analysis of sds/overcommit@fee0cd74b2 (2026-08-23). Data as JSON: /api/errors/e1e4c2e958b33cfe. Report an issue: GitHub.