search

evil-mad / plotink

Common files for Inkscape extensions to drive EggBot, WaterColorBot, and similar plotter-type machines
MIT License
42 stars 29 forks source link

Tag releases #41

Closed notpeter closed 3 years ago

notpeter commented 3 years ago

Hi folks!

Would it be possible to tag the commits which correspond to pypi releases? https://pypi.org/project/plotink/#history

Thanks

oskay commented 3 years ago

Possibly, depending on what it is that you are asking for.

If you are asking if we can update the history at that link, no we cannot. PyPI releases are essentially fixed once published.

If you are asking if we can label commits in this repository with what PyPI release they correspond to, yes, we already do that.

If you are asking something else, please clarify what it is.

notpeter commented 3 years ago

Hi Windell,

I'm asking for the latter: add git tags corresponding to each PyPi Release.
Currently there are no tags for this repo: https://github.com/evil-mad/plotink/tags.

I took 15minutes and I think these are the corresponding hashes for each PyPi release:

Version Date Commit
1.3.1 Oct 13, 2021 a9ed7369d5efd1063ea59e5574961335b5afbed8
1.3.0 Oct 2, 2021 db9580986906e968ff6cc0ec29ceac190d2d5b72
1.2.4 Aug 11, 2021 c99e75610c32dad687133e9dee40b845f87ab8d6
1.2.3 Apr 20, 2021 a45739b7d41b74d35c1e933c18949ed44c72de0e
1.2.2 Dec 21, 2020 c4d18978c1627f3425a9f456e54d40ad5746ff32
1.2.0 Nov 10, 2020 f2cca2190328345a264f727b07b37e8a0e80397c
1.1.0 Sep 28, 2020 2af1764f622e246dfdc7876970342d58761c29c0
1.0.1 Sep 28, 2020 60474ddbf2b96a3178e75da994ffa09303769430
1.0.0 Jul 26, 2020 9ecaeb1f6a6772eb01c8038ab3987b2d3dc3d924

AFAIK there's no GitHub PR flow for proposing tags, but you should be able to create/push them manually.

git tag v1.3.1 a9ed736
git tag v1.3.0 db95809
git tag v1.2.4 c99e756
git tag v1.2.3 a45739b
git tag v1.2.2 c4d1897
git tag v1.2.0 f2cca21
git tag v1.1.0 2af1764
git tag v1.0.1 60474dd
git tag v1.0.0 9ecaeb1
git push --tags

Thanks.

oskay commented 3 years ago

Can I ask what the use case for this is?

notpeter commented 3 years ago

It's pretty standard to tag releases in git and I'd recommend it for all published packages. There are various benefits -- it makes it trivially easy to see a diff between two versioned releases and tell whether there's unreleased code in the main branch. But more generally it's a contract with users -- each released PyPI version number correspond to a commit in this repo -- codified via a tag.

Ultimately it's just metadata. image