-
Notifications
You must be signed in to change notification settings - Fork 27
Tonya 10 19 2024 #385
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
Tonya 10 19 2024 #385
Conversation
Co-authored-by: Drew Lewis <30658947+siwelwerd@users.noreply.github.com>
Co-authored-by: Drew Lewis <30658947+siwelwerd@users.noreply.github.com>
Co-authored-by: Drew Lewis <30658947+siwelwerd@users.noreply.github.com>
Co-authored-by: Drew Lewis <30658947+siwelwerd@users.noreply.github.com>
Co-authored-by: Drew Lewis <30658947+siwelwerd@users.noreply.github.com>
Co-authored-by: Drew Lewis <30658947+siwelwerd@users.noreply.github.com>
Co-authored-by: Drew Lewis <30658947+siwelwerd@users.noreply.github.com>
Co-authored-by: Drew Lewis <30658947+siwelwerd@users.noreply.github.com>
Co-authored-by: Drew Lewis <30658947+siwelwerd@users.noreply.github.com>
🚀 Preview available 🚀 |
@StevenClontz All but the last commit here seem to be from #365, which was already merged into main. What's the best way to deal with that? It seems like it shouldn't be showing a diff on 06-TR/03.ptx and 06-TR/04.ptx, for example, but it is. |
I think a rebase from main will fix the diff, but will break @tdegeorge's Git history, so I'll make that a separate branch and PR. Marking this as draft to move discussion there. |
That doesn't seem to be working. I'll just redo Tonya's work on a new branch. |
No description provided.