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

Use Github releases #3

Open
frederikhors opened this issue Jun 26, 2020 · 2 comments
Open

Use Github releases #3

frederikhors opened this issue Jun 26, 2020 · 2 comments

Comments

@frederikhors
Copy link

Do you mind using Github releases so I can know when there are news?

@estevanmaito
Copy link
Owner

What would be a good approach to it? For real code projects I usually have some automation like semantic-release to make releases, npm publishing and changelog creation.

I'm needing a simpler approach for other projects too, that like this, aren't published packages.

@frederikhors
Copy link
Author

I I would still treat it with the classic semantic: if I add - let's say - a new type of button is a feature, if I fix a problem it is a fix. If there is a feature that breaks something it is a breaking one.

Am I wrong?

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