-
-
Notifications
You must be signed in to change notification settings - Fork 16
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
Token reconstruction runtime sets #32
Conversation
Co-authored-by: fent <[email protected]>
Co-authored-by: fent <[email protected]>
Co-authored-by: fent <[email protected]>
…ocal_token_reconstruction Merging changes from typescript conversion branch
Co-authored-by: fent <[email protected]>
Needed to make importing using the syntax shown in the README valid
Co-authored-by: Charmander <[email protected]>
Co-authored-by: fent <[email protected]>
why create a new PR? the other PR contains lots of discussion that could be useful when looking it over in the future. if it was the last commits you were going to revert, you can submit reverted commits. you can also force push those commits out of history if you wanted to keep history clean |
I'd checked out a new branch at the commit I wanted to revert back to and worked from there so it seemed cleaner to pull the new branch. I have now pushed those changes onto the existing token-reconstruction branch and reponed the respective PR. |
No description provided.