NASA-AMMOS / NASA-AMMOS/AIT-Core
Add workflow for releasing test package to test.pypi
Open
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 56
- Forks
- 35
- Avg merge
- 1d 20h
- Merged PRs (30d)
- 3
Description
Add a GH Actions workflow for packaging the toolkit and pushing it to the test.pypi so we know our packaging is working as expected. Should do this whenever something new is pushed to master or merged I think.
Contributor guide
No contributing guide indexed for this repository
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 the repository's existing GitHub Actions workflows and Python packaging configuration. Determine how the toolkit is packaged and how pushes or merges to master should trigger a TestPyPI publication; done means a workflow can build the package and publish it to test.pypi successfully.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github-actions, python
- Domain
- build-system, ci-cd, release
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100