Automattic / Automattic/harper
ghcr (If you only want to generate images for the variants of Bazzite you are using, edit .github/workflows/build.yml to comment out the variants you do not wish to build in the push-ghcr job's strategy's matrix list) marked as spelling problem
- Dominant language
- Rust
- Stars
- 15.4k
- Forks
- 627
- Avg merge
- 1d 15h
- Merged PRs (30d)
- 106
Description
**What got flagged?**
ghcr
**Why is this incorrect?**
ghcr (If you only want to generate images for the variants of Bazzite you are using, edit .github/workflows/build.yml to comment out the variants you do not wish to build in the push-ghcr job's strategy's matrix list) marked as spelling problem.
Push-to-GHCR is a GitHub Action that simplifies the process of pushing Docker images to the GitHub Container Registry (GHCR) at ghcr.io. It allows you to automate the build and publish process directly from your GitHub repository using workflows.
**Example of correct usage:**
No spelling problems.
Contributor guide
Research direction
Start by locating how Harper handles the flagged term “ghcr” and reproduce the spelling result described in the issue. The only named repository path is .github/workflows/build.yml, specifically the push-ghcr job’s strategy matrix; inspect that context to confirm the expected spelling behavior. Done means “ghcr” is no longer incorrectly marked as a spelling problem.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, github-actions, rust
- Domain
- tooling
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 58/100