Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We鈥檒l occasionally send you account related emails.

Already on GitHub? Sign in to your account

RFE: is it possible to start making github releases?馃 #437

Open
kloczek opened this issue Aug 30, 2023 · 3 comments
Open

RFE: is it possible to start making github releases?馃 #437

kloczek opened this issue Aug 30, 2023 · 3 comments

Comments

@kloczek
Copy link

kloczek commented Aug 30, 2023

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/

@nicoddemus
Copy link
Member

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
Copy link
Author

kloczek commented Aug 30, 2023

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
Copy link
Member

nicoddemus commented Aug 30, 2023

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants