nicoddemus
commented
1 year ago Hi @kloczek,
Nothing against it, we do it for pytest and pytest-mock for example.
If somebody would like to contribute that, I would be happy to review/merge a PR.
Open kloczek opened 1 year ago
nicoddemus
commented
1 year ago Hi @kloczek,
Nothing against it, we do it for pytest and pytest-mock for example.
If somebody would like to contribute that, I would be happy to review/merge a PR.
kloczek
commented
1 year ago It must be some misunderstanding 😊 This RFE has nothing to do with testing. It is ONLY about create GH release entry (visible on https://github.com/pytest-dev/pluggy/releases) which causes that email motivations are sent to those who set on your repo watch->release. You can create GH release even with empty comment because email subject automatically contains git tag name on top of which GH release is added.
nicoddemus
commented
1 year ago It is ONLY about create GH release entry (visible on https://github.com/pytest-dev/pluggy/releases) which causes that email motivations are sent to those who set on your repo watch->release.
No I got it, sorry I was not clear, but if we want to start generating GitHub releases, it should be part of the deployment process, see for example:
That's why I said I would be happy to review/merge a PR in that direction.
Is it possible next time on release new version make the github release to have entry on https://github.com/pytest-dev/pluggy/releases? 🤔
I'm asking because only on make gh release is spread notification about new release to those who have set watch->releases. My automation process those notification trying make preliminary automated upgrade of building packages which allow save some time on maintaining packaging procedures.
More about gh releases is possible to find on https://docs.github.com/en/repositories/releasing-projects-on-github/managing-releases-in-a-repository https://github.com/marketplace/actions/github-release https://pgjones.dev/blog/trusted-plublishing-2023/