generate_og_images.py rewrites every existing OG image on a different machine
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 82/100
Research direction
Start with scripts/generate_og_images.py and inspect how it handles existing PNGs and the --force option. Then review .pre-commit-config.yaml, the make build-explainers target, and the generated-files check, which only verifies presence and size. Update the script and CONTRIBUTING guidance; done means adding one explainer changes only its two OG PNGs, while --force restores regeneration of existing images.
Written by the indexing model from the issue text.
Description
Where: scripts/generate_og_images.py, make build-explainers, .pre-commit-config.yaml.
Current gap: Running make build-explainers after adding one explainer regenerates all OG PNGs, and on macOS with Pillow 11.1.0 every existing PNG in assets/og and assets/og-light comes out byte-different from the committed one, so the diff is hundreds of binary files.
Repro:
$ python3 scripts/generate_og_images.py
$ git status --short assets | wc -l # one line per existing image, not only the new one
Suggested approach: Skip a slug whose PNG already exists unless --force is given (the generated-files check only verifies presence and size), and say so in CONTRIBUTING.
Done when: adding one explainer changes only that explainer's two PNGs, and --force restores the old behaviour.
- Dominant language
- HTML
- Stars
- 47
- Forks
- 45
- Avg merge
- 3h 17m
- Merged PRs (30d)
- 107
Getting set up
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from yakew7/Fair-Code
-
enhancement help wanted tooling
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
Maintainers usually reply within 1 day
-
bug testing
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
Maintainers usually reply within 1 day
-
enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
yakew7/Fair-Code#1169 · 2 comments ·
Maintainers usually reply within 1 day
-
enhancement reproducibility testing
Difficulty 3/5 1-2 days Newbie friendliness 67/100
yakew7/Fair-Code#1205 · 2 comments ·
Maintainers usually reply within 1 day
-
ci community enhancement
Difficulty 4/5 3-5 days Newbie friendliness 52/100
Maintainers usually reply within 1 day
All issues in yakew7/Fair-Code
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
Maintainers usually reply within 1 day
-
bug triage
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
Maintainers usually reply within 1 day
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
bug p2 qa:ui triaged
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
saketh-kowtha/lazyhub#464 ·
Maintainers usually reply within 1 day
-
developer-experience documentation good first issue priority: low testing
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
Gautam-aman/CODOVYN#22 ·