mpfaffenberger / mpfaffenberger/code_puppy
chore: remove emojis from all tracked text
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 814
- Forks
- 278
- Avg merge
- 2d 5h
- Merged PRs (30d)
- 76
Description
Summary
Perform a repository-wide sweep and remove emoji characters from all tracked text. Use concise plain-text replacements where an icon currently carries useful meaning.
Scope
- Scan source code, tests, documentation, comments, docstrings, prompts, configuration, fixtures, examples, and user-facing UI copy.
- Remove emoji Unicode characters from display names, status labels, banners, help text, and other product copy.
- Replace meaningful icon-only labels with accessible plain-text wording rather than silently deleting their meaning.
- Update affected assertions, snapshots, fixtures, and documentation.
- Do not modify binary image assets merely because they depict the mascot; this issue concerns emoji characters in tracked text.
Acceptance criteria
- A reproducible repository scan reports no emoji characters in tracked text files.
- No emoji characters remain in source, tests, documentation, comments, docstrings, prompts, configuration, fixtures, examples, or UI strings.
- An automated check prevents emoji characters from being reintroduced into tracked text.
- Existing behavior remains intact except for the intended copy and presentation changes.
- The full test suite and required linters pass.
Contributor guide
No contributing guide indexed for this repository
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.
Research direction
Start by building a reproducible scan of tracked text files, then use its results to enumerate affected source, tests, documentation, configuration, fixtures, examples, and UI copy. Replace emoji with concise accessible text where meaning is needed, update affected assertions and snapshots, and add an automated check; done means the scan is clean and the full test suite and required linters pass.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- tooling
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100