Adding a zero byte file with no description looks like a Hacktoberfest style, low-effort, low value contribution. That may not BE the case here; I'm just offering one possible explanation to the tepid reaction from the maintainers in the last
I suggest if you are interested in getting this merged (and TBC, I'm not involved with the project, this is just a drive-by review from an experienced open-source maintainer) that you make it easy for the maintainer to click the 'accept' button and take on the life-long care and maintenance of that ... empty file to test, document, and integrate into whatever unnamed environment may use it for whatever purpose.
Please consider making it easy for the reviewers/maintainers to figure out why a PR should be accepted, what bugs/features it addresses, what OSes care about it, links to relvant documentation, included test cases, and all those other things that normally go with a PR.
Of course, if it was your intention for this to be a pending PR while you actually populate it for for this PR to have all those things, this may just be git operational error (soooo easy to do) and the PR itself just need refreshing/updating.
Adding a zero byte file with no description looks like a Hacktoberfest style, low-effort, low value contribution. That may not BE the case here; I'm just offering one possible explanation to the tepid reaction from the maintainers in the last
I suggest if you are interested in getting this merged (and TBC, I'm not involved with the project, this is just a drive-by review from an experienced open-source maintainer) that you make it easy for the maintainer to click the 'accept' button and take on the life-long care and maintenance of that ... empty file to test, document, and integrate into whatever unnamed environment may use it for whatever purpose.
Please consider making it easy for the reviewers/maintainers to figure out why a PR should be accepted, what bugs/features it addresses, what OSes care about it, links to relvant documentation, included test cases, and all those other things that normally go with a PR.
Of course, if it was your intention for this to be a pending PR while you actually populate it for for this PR to have all those things, this may just be git operational error (soooo easy to do) and the PR itself just need refreshing/updating.
Good luck!