Cursor buildllm token context protocol 593a#1645
Conversation
Co-authored-by: nicsins <nicsins@gmail.com>
Co-authored-by: nicsins <nicsins@gmail.com>
Co-authored-by: nicsins <nicsins@gmail.com>
Co-authored-by: nicsins <nicsins@gmail.com>
Co-authored-by: nicsins <nicsins@gmail.com>
Co-authored-by: nicsins <nicsins@gmail.com>
…ous-innovation-agency-3733 Build autonomous innovation agency
Co-authored-by: nicsins <nicsins@gmail.com>
Co-authored-by: nicsins <nicsins@gmail.com>
Co-authored-by: nicsins <nicsins@gmail.com>
![chatgpt-codex-connector[bot]](https://avatars.githubusercontent.com/in/1144995?s=60&v=4){kind=small}
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: f8f256704b
ℹ️ 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".
| run: | | ||
| # NOTE: put your own distribution build steps here. | ||
| python -m pip install build | ||
| python -m build |
There was a problem hiding this comment.
In this workflow, the release job runs python -m build from the repository root immediately after checkout, but I checked the root for pyproject.toml, setup.py, or setup.cfg and none exists. That means every published release will fail in release-build before dist/ is uploaded or PyPI publishing can run; either add package metadata at the root or cd to the package that actually has it before building.
Useful? React with 👍 / 👎.
2 participants
No description provided.