Skip to content
Snippets Groups Projects
Select Git revision
  • renovate/major-opa
  • spike/go-tools-124-gql
  • spike/go-tools-124
  • main default protected
  • chore/deepmap
  • docs/mas
  • build/notify
  • fix/du
  • defect/diff
  • defect/json
  • chore/schema
  • feat/diff-json
  • chore/typo
  • build/binaries
  • build/changelog-
  • defect/otel
  • chore/otel
  • chore/dep
  • docs/changelog
  • defect/changelog
  • v0.115.3 protected
  • v0.115.2 protected
  • v0.115.1 protected
  • v0.115.0 protected
  • v0.114.0 protected
  • v0.113.5 protected
  • v0.113.4 protected
  • v0.113.3 protected
  • v0.113.2 protected
  • v0.113.1 protected
  • v0.113.0 protected
  • v0.112.0 protected
  • v0.111.1 protected
  • v0.111.0 protected
  • v0.110.2 protected
  • v0.110.1 protected
  • v0.110.0 protected
  • v0.109.0 protected
  • v0.108.0 protected
  • v0.107.0 protected
40 results

repository.go

  • Jamie Tanna's avatar
    aea721ad
    chore(db): return better error on `db init` failures · aea721ad
    Jamie Tanna authored
    When we fail to provision tables, for instance via `db init`, we
    would get a very unhelpful error message.
    
    To improve this, we can instead provide a more useful error message,
    which takes advantage of the `Name` for each `Repository` type.
    
    However, this has flagged that a number of repositories haven't yet
    implemented it, so we need to add it.
    
    This is largely _not_ user-facing, as we should only receive these
    errors when we're in development, but it's still worthwhile making the
    changes.
    aea721ad
    History
    chore(db): return better error on `db init` failures
    Jamie Tanna authored
    When we fail to provision tables, for instance via `db init`, we
    would get a very unhelpful error message.
    
    To improve this, we can instead provide a more useful error message,
    which takes advantage of the `Name` for each `Repository` type.
    
    However, this has flagged that a number of repositories haven't yet
    implemented it, so we need to add it.
    
    This is largely _not_ user-facing, as we should only receive these
    errors when we're in development, but it's still worthwhile making the
    changes.
Code owners
Assign users and groups as approvers for specific file changes. Learn more.
repository.go 375 B