coco-workflow: follow-ups from the #394 review (lows)

Open
#395 1 comment 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
54/100
Issue type
Refactor
Clarity
Mostly clear
Activity status
Active
Tech stack
github-actions, shell, yaml
Domain
ci-cd, testing

Research direction

Read the workflow’s reusable path and tests/check-coco-gate.sh, then inspect the review notes from #394. Verify checkout cleanup, reset behavior between cases, and the 300/301-line boundary; done means those changes are covered by passing checks. The YAML-aware hygiene check is framed as a consideration, so its scope needs clarification.

Written by the indexing model from the issue text.

Description

From the GLM stamps on #394 (all lows, no behaviour gap in the check itself):

  • The reusable path copies coco-verifier/ into $RUNNER_TEMP but leaves the checkout in the workspace; delete it after copying (and fix the 'moved' comment).
  • tests/check-coco-gate.sh reset() cleans only .coco; untracked docs from earlier cases accumulate. Clean the whole work tree between cases.
  • Add boundary cases for the no-gate limit: exactly 300 changed code lines passes, 301 fails.
  • pages-style job hygiene is checked by grep; consider a YAML-aware check if the workflow grows.
Dominant language
HTML
Stars
347
Forks
12
Avg merge
2d 16h
Merged PRs (30d)
95

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from coco-research/coco

All issues in coco-research/coco

Similar issues

More DevOps issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.