This repository was archived by the owner on Aug 7, 2024. It is now read-only.
data: fix testimonials that i broke because i had changed my username… #8896
Conversation
This file contains hidden or 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
github-actions
bot
added
the
✍ chore: profile
|
Cheers Krish 🎉🎉 |
|
no bullying lmao dean |
|
web3community.json is being deleted because I made it back when the org was web3community now it is WebXDAO, I am not renaming it because organization profiles are not available in BioDrop rn, so I though removing might be the best idea. |
kkrishguptaa
deleted the
fix-testimonials-that-broke-because-i-had-changed-my-username-some-months-ago
branch
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
3 participants
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.
Okay I got some explanation to do, probably, which I'm not going to do, but here is the fix
it renames my second last username on link free to my current ones which I inconveniently forgot to update the last time in the pr
fixed it @loftwah