Put conda deployment into release env
Nobody has claimed this yet.
- Dominant language
- Jinja
- Stars
- 2
- Forks
- 2
- PR merge metrics
- No merged PRs in 30d
Description
The PyPI deployment is in the 'release' environment. This means that it needs to be approved in order to run. But the conda deployment simply runs.
Should by also put the conda deployment into the 'release' environment?
This can not really be fixed in the copier template. But it affects all repos and I didn't know where else to put it.
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 locating the PyPI and conda deployment definitions in the copier template and compare how the release environment is assigned. Confirm how generated repositories consume this configuration; done means conda deployment also requires release approval consistently across affected repositories.
Written by the indexing model from the issue text.
Assessment
- Domain
- devops, release
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100