aliyun / aliyun/aliyun-openapi-python-sdk

Tag PyPI releases for better distribution

Open
#551 0 comments 2 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Python
Stars
1k
Forks
578
PR merge metrics
No merged PRs in 30d

Description

As a Nixpkgs maintainer, we prefer to package your software from GitHub sources than from PyPI sources. If you'd start tagging your releases with the version number (e.g. v3.2.0) we could do that.

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.

Research direction

Review the repository's current release process and determine where version-numbered Git tags are created. Confirm how releases are published, then update that process so releases receive tags such as v3.2.0 and verify the resulting tag format.

Written by the indexing model from the issue text.

Assessment

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

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.