Pull Requests fail with error
Maintainers usually reply within 2 days
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 35/100
- Issue type
- Bug
- Clarity
- Needs clarification
- Activity status
- Quiet
- Tech stack
- github-actions, tex
- Domain
- ci-cd
Research direction
Start by inspecting the GitHub Actions workflow that runs Typos Action / Spell Check with Typos on pull requests. Reproduce the failing check and determine whether the issue is caused by the workflow or the documented content; done means the spell-check check passes on a pull request.
Written by the indexing model from the issue text.
Description
Describe the bug
All pull requests fail with the following error message:
All checks have failed
1 failing check
failing checksTypos Action / Spell Check with Typos (pull_request) Typos Action / Spell Check with Typos (pull_request)Failing after 10s
- Dominant language
- TeX
- Stars
- 347
- Forks
- 862
- Avg merge
- 2d 11h
- Merged PRs (30d)
- 10
Getting set up
- No Dockerfile or Docker Compose file
- No pull request template
- Read the contributing guide
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 libretro/docs
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
libretro/docs#1195 · 4 comments ·
Maintainers usually reply within 2 days
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
Maintainers usually reply within 2 days
-
bug
Difficulty 1/5 Under an hour Newbie friendliness 88/100
Maintainers usually reply within 2 days
-
Difficulty 1/5 Under an hour Newbie friendliness 65/100
Maintainers usually reply within 2 days
-
bug
Difficulty 1/5 1-3 hours Newbie friendliness 65/100
libretro/docs#960 · 3 comments ·
Maintainers usually reply within 2 days
Similar issues
-
type/bug
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
stackabletech/kafka-operator#1033 · 1 comment ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
Urigo/accounter-fullstack#4583 ·
Maintainers usually reply within 2 days
-
agentic-workflows documentation workflow-editor
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
githubnext/gh-aw-workshop#3966 ·
Maintainers usually reply within 1 day
-
🔒 [IBM OSPO Security Notification] — IBM/Deploy-a-Cloud-Native-Application-that-uses-Generative-AIOpensecurity
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
IBM/Deploy-a-Cloud-Native-Application-that-uses-Generative-AI#7 ·
-
agentic-workflows area/Docs partner/agentic-workflows
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
Maintainers usually reply within 1 day