-
Notifications
You must be signed in to change notification settings - Fork 25
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: added generate-nano-reps
script
#84
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
mistakia
added
need/triage
Needs initial labeling and prioritization
priority/medium
Medium: Good to have, but can wait until someone steps up
kind/maintenance
Work required to avoid breaking changes or harm to project's status quo
status/in-progress
In progress
and removed
need/triage
Needs initial labeling and prioritization
labels
Mar 2, 2024
mistakia
force-pushed
the
feat/generate-nano-reps
branch
2 times, most recently
from
March 3, 2024 03:57
87382f6
to
cfc09f4
Compare
Need to resolve the following conflicts:
Currently, only includes reps with 1000 Nano voting weight which includes some reps with no alias or known fields. Thoughts? @qwahzi I wonder if it should be a requirement where at least one other field is known to be included. |
mistakia
force-pushed
the
feat/generate-nano-reps
branch
from
March 4, 2024 02:45
7d63a0e
to
a002f7e
Compare
mistakia
force-pushed
the
feat/generate-nano-reps
branch
from
March 25, 2024 00:38
a002f7e
to
20e0941
Compare
I have reached out to those operators and requested for clarification on these remaining conflicts
|
mistakia
force-pushed
the
feat/generate-nano-reps
branch
from
March 25, 2024 01:21
20e0941
to
d4d7f49
Compare
mistakia
force-pushed
the
feat/generate-nano-reps
branch
from
March 25, 2024 14:49
d4d7f49
to
fb4dd52
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
kind/maintenance
Work required to avoid breaking changes or harm to project's status quo
priority/medium
Medium: Good to have, but can wait until someone steps up
status/in-progress
In progress
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.
Created a script to reconcile data in the nano.community database with the csv file at
data/nano-reps.csv
. The data indata/nano-reps.csv
will serve as a source of truth moving forward.The only conflicting field I didn't know how to reconcile. Perhaps we can contact them and see what their preference is.
I've also opened a new issue to help ensure discord username freshness: #83