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

Updates example to use v2.0.2 instead of v1 #22

Merged
merged 1 commit into from
Oct 22, 2020
Merged

Conversation

stefanwb
Copy link
Contributor

Signed-off-by: Stefan Wessels Beljaars swesselsbeljaars@schubergphilis.com

@triat
Copy link
Owner

triat commented Oct 20, 2020

Hey @stefanwb,

Thanks for the PR. I'd rather keep it the way it is right now, as it shows an example using a released version. Even if I agree that master should always be production-ready, I'd prefer to keep it on the released version to make sure that people do not get their production down due to a mistake on the branch.

Does this make sense to you?

edit: Would it be possible for you to update the documentation with a v2.x.x tag? (you can put the latest release if you want 👍, thanks)

Signed-off-by: Stefan Wessels Beljaars <swesselsbeljaars@schubergphilis.com>
@stefanwb stefanwb changed the title Updates example to use master instead of v1 Updates example to use v2.0.2 instead of v1 Oct 22, 2020
@stefanwb
Copy link
Contributor Author

Updated the PR as requested! Could you add the label hacktoberfest-accepted to this PR maybe? :) Thanks!

@triat
Copy link
Owner

triat commented Oct 22, 2020

Thanks for the update. I've validated your PR for the hacktoberfest 👍

@triat triat merged commit c0e5a92 into triat:master Oct 22, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants