> In any case, whilst it is likely to be simple to code, it also needs testing, and I have not set up a test instance.
I looked at setting it up and it seems that the instructions are fairly easy to follow : https://github.com/Humbedooh/clc - including docker setup. I am planning to take a stab at helping to improve it over the weekend. Happy to collaborate on that and take a stab at some of the issues you raised (and when I complete that ask you to verify if things are fixed) , but I need some reproducible cases and context on where they were from. Maybe you can clarify some of those with examples and links so that I could do so - which ones you think are easy to follow and get some context? J. On Thu, Sep 2, 2021 at 11:46 PM sebb <seb...@gmail.com> wrote: > On Thu, 2 Sept 2021 at 22:30, Jarek Potiuk <ja...@potiuk.com> wrote: > > > > | The URL is then: <repo> - '.git'/blob/<branch>/<filepath>#L<line> > > > > Question sebb: I saw you forked the repo. > That was for a different issue that was trivial to express in a PR. > > > It is open for contribution - why > > don't you contribute a Pull Request for that ? I cannot understand that. > > From what you write it is super-simple and it would take you less time > than > > writing this email if this is that simple. > > I tend to start by recording issues as I find them, and then decide > which ones I might have time to work on. > > However in this case I did not get a chance to do so before I got a > push-back. > If the PR is unlikely to be accepted, I'm not keen to work on it. > > In any case, whilst it is likely to be simple to code, it also needs > testing, and I have not set up a test instance. >
