Invoke deploy should require a tag
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 6
- Forks
- 1
- PR merge metrics
- No merged PRs in 30d
Description
Right now invoke deploy deploys whatever current version is checked out. This means that unless one is careful it's easy to deploy the master branch by mistake instead of the tagged version. Moreover, it should be disallowed to deploy a version that is not properly tagged.
invoke deploy should be rewritten to require a tag argument. The code should then checkout that tag, deploy it, and revert to HEAD.
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 at the implementation of the invoke deploy command and trace how its current checkout and deployment target are selected. Update the command so a tag is required, that tag is checked out for deployment, and the repository returns to HEAD afterward; verify that untagged deployment is rejected.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- cli, devops
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Clearly specified
- Newbie friendliness
- 55/100