After seeing @kartikm's test page in the screenshots of issue #50, I thought it would be a good idea to have a live test in this repo. I created a gh-pages branch in my fork and the resulting test page is accessible here: http://waldir.github.io/AutonymFont/test.html
However, I can't make a pull request because the gh-pages branch doesn't exist upstream, so I'm asking for comments on several things:
Is it a good idea to have such a test page? Note that the branch has to include local copies of the compiled fonts as well as the ULS scripts, which aren't automatically kept up to date with the corresponding sources. I renamed the files to make their versions clear.
Would it work if a gh-pages branch were created in the upstream repo? Would the fact that the two gh-pages branches wouldn't share common ancestors be an issue?
If the above doesn't work, I suppose the workaround is to have @santhoshtr cloning my repo and pushing the new branch upstream.
santhoshtr
commented
10 years ago
After seeing @kartikm's test page in the screenshots of issue #50, I thought it would be a good idea to have a live test in this repo. I created a
gh-pagesbranch in my fork and the resulting test page is accessible here: http://waldir.github.io/AutonymFont/test.htmlHowever, I can't make a pull request because the
gh-pagesbranch doesn't exist upstream, so I'm asking for comments on several things:gh-pagesbranch were created in the upstream repo? Would the fact that the twogh-pagesbranches wouldn't share common ancestors be an issue?