Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

CI: decide on export_test.sh and job_test.sh

Open
#5 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
1-2 days
Newbie friendliness
49/100
Issue type
Refactor
Clarity
Mostly clear
Activity status
Active
Tech stack
docker, python, shell
Domain
ci-cd, testing

Research direction

Read the CI configuration, tests/export_test.sh, tests/job_test.sh, and scripts/export-repo.sh; the issue does not name the CI file. First check how existing CI jobs run tests/cli_test.sh and what runner image the etchwork job test needs. Done means each script is either retired with its one-time or unavailable dependency accounted for, or wired into CI with the required runner image.

Written by the indexing model from the issue text.

Description

ci

CI runs the engine suite and tests/cli_test.sh. Two other scripts aren't in CI:

  • tests/export_test.sh tests scripts/export-repo.sh, the one-time extraction from flai. Probably retire both.
  • tests/job_test.sh tests etchwork job; it needs a runner image, which needs flai (see the runner issue).

Retire or wire each into CI.

Dominant language
Python
Stars
1
Forks
1
Avg merge
1h 36m
Merged PRs (30d)
2

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 FlologixAI/etchwork

All issues in FlologixAI/etchwork

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.