-
Notifications
You must be signed in to change notification settings - Fork 0
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
feat!: upload to flamegraph.com #36
Conversation
why doees it have both |
|
Even though it's a breaking change I think we should:
That way everything is very explicit |
🤖 I have created a release *beep* *boop* --- ## [2.0.0](v1.3.0...v2.0.0) (2023-03-02) ### ⚠ BREAKING CHANGES * upload to flamegraph.com ([#36](#36)) ### Features * upload to flamegraph.com ([#36](#36)) ([a459bbd](a459bbd)) --- This PR was generated with [Release Please](https://github.com/googleapis/release-please). See [documentation](https://github.com/googleapis/release-please#release-please).
Add another flag
--uploadToPublicAPI
that uploads to flamegraph.comExample:
Also rename other flags: