This repository has been archived by the owner on Apr 4, 2023. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 2
feat: add contributor profile dashboard #25
Merged
Rustin170506
merged 21 commits into
ti-community-infra:main
from
Mini256:mini256-metrics
May 6, 2021
Merged
feat: add contributor profile dashboard #25
Rustin170506
merged 21 commits into
ti-community-infra:main
from
Mini256:mini256-metrics
May 6, 2021
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
[REVIEW NOTIFICATION] This pull request has not been approved. To complete the pull request process, please ask the reviewers in the list to review by filling The full list of commands accepted by this bot can be found here. Reviewer can indicate their review by writing |
ti-chi-bot
added
the
do-not-merge/work-in-progress
Indicates that a PR should not merge because it is a work in progress.
label
Apr 27, 2021
ti-chi-bot
added
the
size/M
Denotes a PR that changes 30-99 lines, ignoring generated files.
label
Apr 27, 2021
ti-chi-bot
added
size/XL
Denotes a PR that changes 500-999 lines, ignoring generated files.
and removed
size/M
Denotes a PR that changes 30-99 lines, ignoring generated files.
labels
Apr 29, 2021
ti-chi-bot
added
size/XXL
Denotes a PR that changes 1000+ lines, ignoring generated files.
and removed
size/XL
Denotes a PR that changes 500-999 lines, ignoring generated files.
labels
Apr 29, 2021
Mini256
changed the title
feat: add single contributor dashboard
feat: add contributor profile dashboard
Apr 30, 2021
ti-chi-bot
removed
the
do-not-merge/work-in-progress
Indicates that a PR should not merge because it is a work in progress.
label
May 6, 2021
1 task
Rustin170506
suggested changes
May 6, 2021
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
Prepare
The following steps are to prepare for adding a new metrics:
We can add the new metrics series config in the
test/data/test_metrics.yaml
file and usetest_metric_sync.sh
script to test our new metrics, also we can add the new tags config in thetest/data/test_tags.yaml
file and usetest_tags.sh
script to test our new tags.The SQL file used for the test can be added to the
configs/dev/metrics/shard
directory, or the project directoryconfigs/dev/metrics/{project_name}
specified in the script file, and the test script will preferentially read the sql in the project directory file.We can execute the script locally, the premise is that the PostgresSQL instance used by devstats already exists locally, and the data have imported from gharchive exists in the database.
Add a new metrics
The following steps indicates how to add a new metrics:
devstats/metrics/shard
ordevstats/metrics/kubernetes
to theconfigs/dev/test
, if there is SQL with similar functions as the new metrics. (fa9a49e)For this PR, I removed the symbol ` in the series field and modify the tags table name
tusers
totall_users
:Preview
Related Issue
close #18
todo #26