David Wong
David Wong
OK I think I know what's happening... I already have a repository `opam-repository` which is a fork of a custom opam repository. So I guess there is some collision here?...
Now I'm getting an error at an earlier step: ``` [-] Pushing tag 0.1 to [email protected]:mimoo/hexstring.git [?] Create release 0.1 on [email protected]:mimoo/hexstring.git? [Y/n] [-] Creating release 0.1 on [email protected]:mimoo/hexstring.git via...
It seems like it worked, until I got this: ``` [-] Preparing pull request to ocaml/opam-repository [-] Fetching https://github.com/ocaml/opam-repository.git#master [-] Checking out a local release-hexstring-0.1.1 branch [-] Pushing release-hexstring-0.1.1 to...
> just properly set it up the first time if I understand correctly this only work if you only/most often release to the same custom opam repository. But I imagine...
Ah I see. So if I understand correctly this is the command I should run to submit a PR on `org/opam` with my fork on `mimoo/opam` cloned locally in `path/to/local/mimoo/opam`:...
Amazing, thanks a lot!
I'm having the same issue, the images it creates are too big and don't respect the width of the container in css
I managed to fix this issue like this: ``` $('svg').removeAttr('viewBox'); $('svg').each(function () { let svg = $(this)[0]; let bbox = svg.getBBox(); svg.setAttribute("viewBox", bbox.x + ' ' + bbox.y + '...
of course this doesn't work if you run this before the SVGs have finished loading...