Gnome-Search-Tool don't open containers folders of files after a search in 16.04

Status changed to 'Confirmed' because the bug affects multiple users.

This package "gnome-search-tool" is quite excellent and I use it for a long time, up to 14.04 trusty now. But, Unfortunately, it presents a bad bug with 16.04 xenial :
→ Gnome-Search-Tool don't open containers folders of files after a search in 16.04 ← as said higher.
It's very very annoying. The feature “open containers folders of files after a search” is a essential function of the program.
This function continues to work with Nemo by default but I don’t want to use Nemo.
A replacement solution is Catfish, but this program is very very slow and I much prefer “gnome-search-tool”.
Do you intend to fix this bug in the future? Many users would be delighted.
I would be glad if you could indicate a fix to solve this embarrassing problem, (or better?) if you take time to update this excellent package for being entirely operational with 16.04 xenial.

gboolean
open_file_with_filemanager (GtkWidget * window,
                            const gchar * file,
                            gboolean open_parent)
{
 GDesktopAppInfo * d_app_info;
 GKeyFile * key_file;
 GdkAppLaunchContext * ctx = NULL;
 GList * list = NULL;
 GAppInfo * g_app_info;
 GFile * g_file;
 gchar * command;
 gchar * contents;
 gchar * uri;
 gboolean result = TRUE;

 if (open_parent == TRUE && g_file_test (file, G_FILE_TEST_IS_DIR)) {
  gchar * folder = g_path_get_dirname (file);
  uri = g_filename_to_uri (folder, NULL, NULL);
  g_free (folder);
 }
 else {
  uri = g_filename_to_uri (file, NULL, NULL);
 }
...

The problem is at:
   if (open_parent == TRUE && g_file_test (file, G_FILE_TEST_IS_DIR)) {
should be:
   if (open_parent == TRUE && g_file_test (file, G_FILE_TEST_IS_REGULAR)) {

I've made a 'pull request' to fix this bug, in:
https://github.com/GNOME/gnome-search-tool/pulls

But I don't know if my 'pull request' will be accepted.
I don't know how to contribute with code. Can anyone help-me with this?

This bug is still alive more than two years later. My machine: Ubuntu 16.04.5 LTS. Please, it would be most useful correcting this.