Publish to PyPI so pipx install windows-autoclicker works

未關閉
#118 1 則留言 0 個 reaction 已指派 0 人 在 GitHub 檢視

維護者通常 3 天內回覆

還沒有人認領這個 Issue。

評估

難度
4/5
預估耗時
3-5 天
新手友好度
38/100
Issue 類型
功能
描述清晰度
基本清楚
活躍度
冷清
技術堆疊
github-actions, python

研究方向

Start with pyproject.toml and the tag release workflow; the issue also points to README lines 137–140 and the landing page install section. Review the metadata cleanup dependency before reserving the package name, then check the release workflow’s build and publishing steps. Done means tagged releases publish checked wheel and sdist artifacts and pipx install windows-autoclicker installs the latest release.

由索引模型根據 Issue 內容生成。

描述

marketing packaging priority: low

Why it matters

Python users and scripters (the CLI/headless audience) expect pipx install <name>. Today the README tells them to install from a git URL, which is slower, harder to pin and invisible to PyPI search.

Evidence

  • README:137-140 recommends pipx install git+https://github.com/TMHSDigital/autoclicker.git.
  • https://pypi.org/pypi/windows-autoclicker/json returns 404; the name is free.
  • pyproject.toml already has a complete [project] table and #58 fixed wheel icons.

Suggested approach

  • Add a pypi job to the tag release using Trusted Publishing (OIDC, no stored token), building sdist + wheel with python -m build and running twine check.
  • Reserve the name now with a 1.6.x upload.
  • Update README and landing page install sections; add a PyPI badge.
  • Depends on the metadata cleanup issue so the PyPI page looks right.

Done when

pipx install windows-autoclicker installs the latest release, and the release workflow publishes automatically on tags.

主要語言
Python
星號
0
分支
2
平均合併
2 天 13 小時
30 天內合併 PR
2

環境準備

從這裡開始

  1. 先讀完整個 Issue,再讀專案的貢獻指南。
  2. 在 Issue 下留言說明你要接手 —— 這能避免兩個人做同樣的事。
  3. Fork 儲存庫,在一個分支上完成修改。
  4. 送出 Pull Request,並在描述裡引用這個 Issue 編號。

TMHSDigital/autoclicker 的其他 Issue

查看 TMHSDigital/autoclicker 的全部 Issue

相似的 Issue

更多 Python Issue

把新 issue 寄到你的電子郵件信箱

精選適合新手參與的 GitHub issue 摘要。