Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

[Request] Use tags when creating releases

Open
#38 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
35/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Stale
Tech stack
git, github, python
Domain
release

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.

Description

enhancement

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

Dominant language
Python
Stars
191
Forks
31
No merged PRs in 30d

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from localstack/localstack-python-client

All issues in localstack/localstack-python-client

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.