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

No previously recorded signature for configuration file. Run

Error message

No previously recorded signature for configuration file.
Run `overcommit --sign` if you trust the hooks in this repository.

What it means

Error "No previously recorded signature for configuration file. Run `overcommit --sign` if you trust the hooks in this repository." thrown in sds/overcommit.

Source

Thrown at lib/overcommit/configuration_loader.rb:94

      if @options.fetch(:verify) { config.verify_signatures? }
        verify_signatures(config)
      end

      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 hooks in this repository, then run `overcommit --sign` to record a trusted signature for the configuration file.
2. If you do not trust the repository's hooks, do not sign; skip the run or disable signature verification with OVERCOMMIT_NO_VERIFY at your own risk.

When it happens

Trigger: Thrown at lib/overcommit/configuration_loader.rb:94 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/98493be4a9311175. Report an issue: GitHub.