Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Post issues for users
See original GitHub issueWhen users first use Font Bakery to check their project, they may want to run Font Bakery’s command line tool against their repo, in the same way that the dashboard can ingest a repo.
The most simple thing I can think of is that FB should accept URLs along with directory paths or a set of file paths. However, perhaps it is better to have a new ‘shorthand’ command, like
fontbakery check-googlefonts-github git@github.com:username/project
Following on from this, I can see that users of Font Bakery may wish to ‘spray’ their Github Issue tracker with one issue per failed check, like Eli did for himself just now:
Perhaps a command like one of these,
fontbakery check-googlefonts-github git@github.com:username/project --post-issues
fontbakery check-googlefonts-github-and-post git@github.com:username/project
would mean that, after the complete check results are printed, for each fail it asks you y/[n] style if you want to auto-post an issue.
-
And in the case you already ran FB and want to ‘firehose spray’ the issue tracker with everything, there should be a mode to to ‘auto post’ all, like :
fontbakery check-googlefonts-github git@github.com:username/project --post-issues --yes fontbakery check-googlefonts-github git@github.com:username/project --post-issues --hard fontbakery check-googlefonts-github-and-post git@github.com:username/project --auto
etc
Issue Analytics
- State:
- Created 5 years ago
- Comments:11 (8 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
gftools qaalready posts qa reports back to repos automatically. If it’s checking a pr, it will post it as an issue to the pr (how the ci currently works on google/fonts). If it’s a dir containing fonts binaries, it opens a new issue.Nice. I look forward to seeing what you come up with. It may be a good idea to add this functionality once we’ve fixed most of the checks which produce false positives.
We should start planning how we should share these functions across our tools/libs. I’ve probably written a function to download families from Google Fonts three times. It would be nice to have such code consolidated into a single lib or added to an existing one. This may also be a terrible idea but imo it’s worth discussing.