Parse subject and body for a commit message and convert urls into links.
It is possible to read custom links config from ./git/config ini file:
example to parse issues and merge request for gitlab:
```
[gitg.custom-link "issues"]
regexp=!([0-9]+)
replacement=https://gitlab.gnome.org/GNOME/gitg/merge_requests/\1
color = orange
[gitg.custom-link "merge.request"]
regexp=#([0-9]+)
replacement=https://gitlab.gnome.org/GNOME/gitg/merge_requests/\1
color = green
```
Avoid use deprecated method to update font
Co-authored-by: Adwait Rawat <adwait.rawat@gmail.com>
Co-authored-by: Gaurav Agrawal <agrawalgaurav1999@gmail.com>
meson: set the schema path correctly
window: fix single quotes
python habits
meson: fix various issues with dual installation
Flatpak: don't enforce the branch for gitg
It causes issues with Gitlab CI as we can't test the build on other branches anymore.
remove .gitignore
The GObject Introspection metadata generation by meson uses a custom
target command[0]. This command also needs to specify the shared
library where the symbols in the typelib file can be found.
However, the values used are wrong because the path to the built
shared libraries are specified instead of the name of the
shared libraries themselves.
This has been fixed by specifying the name of the shared libraries.
Fixes#157
[0] http://mesonbuild.com/Vala.html#gobject-introspection
Although most of the parameters used for file naming when building
libraries and introspection data can be replaced by variables, the
actual naming can create a lot of confusion.
This naming scheme has been improved by using clearer names and by
also using a prefix in them.
Libraries build by gitg expose a number of includes in their public
headers belonging to different libraries. Therefore, these libraries
are indirect dependencies of the library to be built.
With this in mind, these indirect dependencies are also included
when a direct dependency is included, so there is no need to include
them again.
Dependency hierarchy has been fixed and duplicated dependencies
removed.
Created `pkg-config` files requirements have also been fixed.
Some targets that are installed in default directories are using the
`install_dir`, which is not necessary.
The `install_dir` parameter has been removed from those targets that
are installed in their default directories.
We need to instance a Gtk.Widget to be able to use `get_style_context`.
Thus, we use the singleton pattern to avoid allocating an object every
time we call `is_theme_dark()`.
Fixes#133.
While installing seems to have no issues with absolute paths
for install_dir, the pkgconfig integration in meson does
and create wrong library paths in the .pc file.
https://bugzilla.gnome.org/show_bug.cgi?id=788796
