-
Notifications
You must be signed in to change notification settings - Fork 3.2k
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
Basic implementation of robust message revision proposal system #3289
Conversation
❌ pre-commit failed. |
was going to ask if edits will be stored and tracked and looks like you thinking yes - this is cool as this could actually end up being very high quality metadata for various use cases. love idea of edits being almost like git diffs in some ways. |
Thank you, please keep in mind that other contributor is working on something that touches upon this work here #3280 Feel free to get in touch on discord to coordinate |
❌ pre-commit failed. |
❌ pre-commit failed. |
❌ pre-commit failed. |
❌ pre-commit failed. |
1 similar comment
❌ pre-commit failed. |
❌ pre-commit failed. |
1 similar comment
❌ pre-commit failed. |
❌ pre-commit failed. |
Couldn't get to coding this month because I am moving, but I will get back to work on this PR from now on because I am somewhat stable. The work I can put on this is basically weekly, something like 2 days of the week, but I have not left this PR behind. If someone is interested in helping me finish the PR sooner I can add you to the contributors on my OA fork. |
❌ pre-commit failed. |
Hello, this is the pull request intending to implement a basic editing system.
The revision proposal system I am planning to write is going to include the following features (as mentioned in #3185):
Current changes
My discord username is
gabrielmfern
if anyone anyone wants to discuss something in more detail directly with me