Skip to content

Add Python package scaffolding and CI tooling - #1

Merged
tmgsr02 merged 1 commit into
masterfrom
codex/initialize-git-repository-and-project-structure
Oct 24, 2025
Merged

tmgsr02 merged 1 commit into
masterfrom
codex/initialize-git-repository-and-project-structure

Conversation

@tmgsr02

@tmgsr02 tmgsr02 commented Oct 24, 2025

Copy link
Copy Markdown
Owner

Summary

  • add a Hatch-based pyproject.toml for the new macrobase-py package with core dependencies and dev tooling configuration
  • scaffold the macrobase_py package layout and update repository documentation and ignores for Python development
  • configure pre-commit hooks and a GitHub Actions workflow to lint and run tests across Python 3.9+

Testing

  • python -m compileall macrobase_py

https://chatgpt.com/codex/tasks/task_e_68fade0a3a008320af470514fbf23927

@tmgsr02
tmgsr02 merged commit 3d97a6b into master Oct 24, 2025
0 of 8 checks passed

@chatgpt-codex-connector chatgpt-codex-connector Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

💡 Codex Review

Here are some automated review suggestions for this pull request.

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

Comment on lines +38 to +40
- name: Run tests
run: |
hatch run pytest

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P1 Badge Avoid unconditional pytest run with no test suite

The workflow always executes hatch run pytest, but this repository currently has no Python test files (find . -name "test_*.py" -o -name "*_test.py" returns nothing). Pytest exits with status code 5 when zero tests are collected, so the new CI job will fail on every push even though there is nothing to run. Consider guarding the step or using an option such as pytest --maxfail=0 --disable-warnings --allow-empty until tests exist so the pipeline can pass.

Useful? React with 👍 / 👎.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant