-
Notifications
You must be signed in to change notification settings - Fork 3
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
Fix version and update dependencies #106
Conversation
1. `export EXOSCALE_API_KEY=<the-key>` | ||
1. `export EXOSCALE_API_SECRET=<the-secret>` | ||
1. `make local-install` | ||
2. `export EXOSCALE_API_KEY=<the-key>` |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
No need to manually increment here. Most markdown renderers will do that for you.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Well as you can see the previous markdown didn't work quite well lol :D
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The current readme shows fine for me though?
https://github.com/vshn/provider-exoscale/blob/master/README.md#quickstart-demonstration
Be aware that the source code will not automatically increment the numbering, it's only in the rendered version.
But anyway it's just a nitpick.
Checklist
changelog.
The PR has a meaningful description that sums up the change. It will be
linked in the changelog.
make test-e2e
locally.bug
,enhancement
,documentation
,change
,breaking
,dependency
as they show up in the changelog.