Auto-sync generation failure (6e8a01c)
Maintainers usually reply within 2 days
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 65/100
- Issue type
- Bug
- Clarity
- Mostly clear
- Activity status
- Active
- Tech stack
- javascript
- Domain
- build-system, ci-cd
Research direction
Start with the linked workflow run and .github/workflows/generate.yaml to identify the full error. Then inspect the affected entries in rules.manifest.yaml and the guidance in docs/plans-archive/docs-driven-skills.md, Story 4. Done means correcting the source or manifest issue, running npm run generate -- --docs-path , and opening a fix PR.
Written by the indexing model from the issue text.
Description
Auto-sync generation failed for docs SHA 6e8a01cb3fa5510c79833ae1148119d97a9abe45.
Opened automatically by .github/workflows/generate.yaml. Check the workflow run for the full error.
Common causes and fixes (Story 4 in docs/plans-archive/docs-driven-skills.md):
- Source file renamed or moved — update
sources[].pathinrules.manifest.yaml. - Section heading renamed or removed — update
sources[].section. - Must-cover assertion no longer in source — update
must_coveror the section changed. - Regeneration dropped a fact its sources still document — the model restructured a
rule and lost content. Re-run generation, or if the removal is correct, record it
underrules[<slug>].allow_droppedin the manifest.
After fixing, regenerate locally (npm run generate -- --docs-path <docs>) and open a fix PR.
- Dominant language
- JavaScript
- Stars
- 3
- Forks
- 0
- Avg merge
- 2d 13h
- 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 HarperFast/skills
-
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
HarperFast/skills#96 ·
Maintainers usually reply within 2 days
-
good first issue
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
HarperFast/skills#21 · 2 comments ·
Maintainers usually reply within 2 days
-
harper-best-practices teaches un-awaited MaybePromise bodies and the legacy instance-verb form (with the wrong argument order)May be free again @kriszyp claimed this 62 days ago, and no pull request is open. Open
HarperFast/skills#79 · 3 comments · 1 assignee ·
Maintainers usually reply within 2 days
-
Difficulty 3/5 1-2 days Newbie friendliness 72/100
HarperFast/skills#78 ·
Maintainers usually reply within 2 days
-
good first issue
Difficulty 2/5 1-3 hours Newbie friendliness 55/100
HarperFast/skills#29 ·
Maintainers usually reply within 2 days
All issues in HarperFast/skills
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
bigcalendar/react-big-calendar#2823 ·
-
feature t-tooling
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
Maintainers usually reply within 1 day
-
neutral:fix
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 1 day
-
documentation enhancement
Difficulty 1/5 Under an hour Newbie friendliness 85/100
OWASP/cve-lite-cli#1480 ·
Maintainers usually reply within 2 days