quick sketch of how the retrieval of ints from config could look like (#298)

However, I think this should really be part of `config` itself,
while the `Repository` provides some utilities at best to deal with
mutability maybe.

Author: Byron

git-repository/src/lib.rs

@@ -234,10 +234,6 @@ mod config {
     pub mod open {
         pub type Error = git_config::parser::ParserOrIoError<'static>;
     }
-    ///
-    pub mod query {
-        pub type Error = git_config::file::GitConfigError<'static>;
-    }
 }
 
 ///

git-repository/src/repository/config.rs

@@ -1,9 +1,12 @@
-use crate::config;
-
 /// Provide simplified access to git configuration values
 impl crate::Repository {
     /// Return the integer value at `key` (like `core.abbrev`) or use the given `default` value if it isn't present.
-    pub fn config_int(_key: &str, _default: i64) -> Result<i64, config::query::Error> {
-        todo!()
+    // TODO: figure out how to identify sub-sections, or how to design such an API. This is really just a first test.
+    // TODO: tests
+    pub fn config_int(&self, key: &str, default: i64) -> i64 {
+        let (section, key) = key.split_once('.').expect("valid section.key format");
+        self.config
+            .value::<git_config::values::Integer>(section, None, key)
+            .map_or(default, |v| v.value)
     }
 }