localstack / localstack/localstack-python-client
[Request] Use tags when creating releases
Open
Nobody has claimed this yet.
enhancement
- Dominant language
- Python
- Stars
- 191
- Forks
- 31
- PR merge metrics
- No merged PRs in 30d
Description
Trying to package localstack for Nixpkgs. Wanted to pull in tests from github to ensure that localstack-client works, however, it's hard to know which commit was used for a particular release.
Related to: https://github.com/localstack/plux/issues/4
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
The issue names no file, test, or release entry point. Start by inspecting how releases are currently created and compare that process with the related localstack/plux issue; done means each release has a tag that identifies the exact commit used.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- git, github, python
- Domain
- release
- Issue type
- Feature
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100