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’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

RFE: is it possible to start making github releases?🤔 #139

Closed
kloczek opened this issue Aug 30, 2023 · 2 comments · Fixed by #140
Closed

RFE: is it possible to start making github releases?🤔 #139

kloczek opened this issue Aug 30, 2023 · 2 comments · Fixed by #140

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/ESSS/pytest-regressions/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 added a commit that referenced this issue Aug 31, 2023
Also modernize how the package is generated using `build` instead of deprecated `setup.py`.

Close #139
@nicoddemus
Copy link
Member

Thanks @kloczek, opened #140 with an attempt to do that. 👍

nicoddemus added a commit that referenced this issue Aug 31, 2023
Also modernize how the package is generated by using `build` instead of deprecated `setup.py`.

Close #139
@kloczek
Copy link
Author

kloczek commented Aug 31, 2023

Thank you very much 👍 😄

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

Successfully merging a pull request may close this issue.

2 participants