pyiron / pyiron/pyiron_module_template
Use hatch
Nobody has claimed this yet.
- Dominant language
- Shell
- Stars
- 0
- Forks
- 0
- PR merge metrics
- No merged PRs in 30d
Description
Based on the usage of hatch in executorlib, I added a new release workflow to the centralized actions that uses hatch instead of setuptools. The application in bagofholding involved a number of small changes but nothing crazy and serves as a template for the updates needed to switch over here.
I didn't remove the setuptools workflow in pyiron/actions and have no plans to do so, so the old way should keep working for the foreseeable future.
Contributor 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.
Research direction
Start by inspecting this repository’s current setuptools release workflow and compare it with the bagofholding PR #50 and centralized pyiron/actions PR #153. Done means the module template uses the hatch-based release workflow while the existing setuptools workflow remains supported.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github-actions, python
- Domain
- build-system, ci-cd
- Issue type
- Refactor
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100