-
Notifications
You must be signed in to change notification settings - Fork 623
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
Uses area chart instead of line chart #98
Merged
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oh wow, yeah that looks great! Would it be possible to invert it as well? I think we'd like to have the most recent version show up on top (in the legend and in the chart itself). |
Nice! Thanks for this! |
alexcrichton
added a commit
that referenced
this pull request
Dec 30, 2014
Uses area chart instead of line chart
bors
added a commit
that referenced
this pull request
Dec 17, 2019
…d-5.0.0, r=Turbo87 Bump ember-keyboard from 4.0.0 to 5.0.0 Bumps [ember-keyboard](https://github.com/patience-tema-baron/ember-keyboard) from 4.0.0 to 5.0.0. <details> <summary>Release notes</summary> *Sourced from [ember-keyboard's releases](https://github.com/patience-tema-baron/ember-keyboard/releases).* > ## upgrade ember-cli-babel > upgrades to ember-cli-babel 7. </details> <details> <summary>Commits</summary> - [`cba9aef`](adopted-ember-addons/ember-keyboard@cba9aef) bump - [`0ba6863`](adopted-ember-addons/ember-keyboard@0ba6863) Merge pull request [#94](https://github-redirect.dependabot.com/patience-tema-baron/ember-keyboard/issues/94) from Gaurav0/babel_7 - [`63f013b`](adopted-ember-addons/ember-keyboard@63f013b) Merge pull request [#102](https://github-redirect.dependabot.com/patience-tema-baron/ember-keyboard/issues/102) from gabrielgrant/patch-1 - [`ddb0f11`](adopted-ember-addons/ember-keyboard@ddb0f11) Update README to fix docs link - [`32df04e`](adopted-ember-addons/ember-keyboard@32df04e) Merge pull request [#98](https://github-redirect.dependabot.com/patience-tema-baron/ember-keyboard/issues/98) from MelSumner/patch-1 - [`6b7a740`](adopted-ember-addons/ember-keyboard@6b7a740) Update README.md - [`2d3a8af`](adopted-ember-addons/ember-keyboard@2d3a8af) Upgrade to babel 7 - See full diff in [compare view](adopted-ember-addons/ember-keyboard@v4.0.0...v5.0.0) </details> <br /> [![Dependabot compatibility score](https://api.dependabot.com/badges/compatibility_score?dependency-name=ember-keyboard&package-manager=npm_and_yarn&previous-version=4.0.0&new-version=5.0.0)](https://dependabot.com/compatibility-score.html?dependency-name=ember-keyboard&package-manager=npm_and_yarn&previous-version=4.0.0&new-version=5.0.0) Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting `@dependabot rebase`. [//]: # (dependabot-automerge-start) [//]: # (dependabot-automerge-end) --- **Note:** This repo was added to Dependabot recently, so you'll receive a maximum of 5 PRs for your first few update runs. Once an update run creates fewer than 5 PRs we'll remove that limit. You can always request more updates by clicking `Bump now` in your [Dependabot dashboard](https://app.dependabot.com). <details> <summary>Dependabot commands and options</summary> <br /> You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself) - `@dependabot use these labels` will set the current labels as the default for future PRs for this repo and language - `@dependabot use these reviewers` will set the current reviewers as the default for future PRs for this repo and language - `@dependabot use these assignees` will set the current assignees as the default for future PRs for this repo and language - `@dependabot use this milestone` will set the current milestone as the default for future PRs for this repo and language - `@dependabot badge me` will comment on this PR with code to add a "Dependabot enabled" badge to your readme Additionally, you can set the following in your Dependabot [dashboard](https://app.dependabot.com): - Update frequency (including time of day and day of week) - Pull request limits (per update run and/or open at any time) - Automerge options (never/patch/minor, and dev/runtime dependencies) - Out-of-range updates (receive only lockfile updates, if desired) - Security updates (receive only security updates, if desired) </details>
Turbo87
pushed a commit
to Turbo87/crates.io
that referenced
this pull request
Jan 4, 2023
…bscriber-0.3.x
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This addresses #95.
Here are some screenshots for comparison. These charts are from the gcc crate:
Ultimately this has a lot to do with personal preference so I understand if the line charts are preferred over the area charts. This ended up being a one line fix so no big deal either way.