-
Notifications
You must be signed in to change notification settings - Fork 76
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
Move To Brain Brew #364
Move To Brain Brew #364
Conversation
I am not an expert of Git Actions, so I will not mess with the previous system that ran the The build recipe can be verified with |
AFAIR, the ultimate goal is to move to a single However, I think that it might be worth switching to IMO the most important thing missing is having the CSS and templates as separate files. I have doubts whether per-field CSVs ( Also, congratulations on (soon) becoming a father! |
I also don't mind if we keep the data in CSV files for now. It actually makes the transition smoother I think.
Yeah, I agree -- merging without this would be a step back, I think. That being said, it's not a huge deal either, so if it postpones the move to BB too much, I wouldn't mind merging without it. |
This looks fantastic! Unfortunately, I won't have time for more than the cursory look I've had (or to test the conversion pathways/recipes) in the nearest future, but I think that it'd be great to get this merged soon! Three things that might be valuable (but I don't think are essential before merging (not that it's up to me 😃)):
|
Thanks! I just have a quick change to make so the deck description can live as it's own Html file too, and a bugfix about the importing media from CrowdAnki going in the right subfolder instead of the top level media folder. Then I'll release the latest version of Brain Brew, and point UG towards that 👍 (currently still running off my latest local branch).
No problem mate, but I hope so too!
|
Great! :)
I was thinking about something equivalent to the "install" and "running" steps from your Brain Brew Starter Readme, to replace the |
Alright, all apart from the update to Contributing is now done 👍 I have released Brain Brew 0.2.5, which brings the changes I mentioned above:
I have also added the The Extended Deck works, each language is working too. All the html and css files live on their own (though the downside is these lone html and css files cannot be written to in a This is a great time for me to update my own Brain Brew documentation, as so much has changed since I last touched it, it is very out of date. I will in tandem update the Contributing here, but would like some sanity checking that everything seems to work first. No rush, it can wait until the new year. I hope Brain Brew will be used in UG by the end of January! 😁 👏 Lemme know if you guys spot anything, whenever you have time. Thanks again for your hard work 👍 |
Wow, that was amazingly fast! I'll try to have a detailed look ASAP and definitely before the New Year (I hope...)! |
Only a few months! 😆 I finally had a good amount of free time today, for once in the last few months 😉 |
Oh, I should of course do a pull of the latest UG again. And I am sure an update to the Workflow files would be appreciated too. |
2bdcf04
to
e52b243
Compare
Rebased onto latest, and updated the workflow to do a full build and check for errors 👍 Just have to make changes to the Contributing. At a glance I can see I should:
See anything else I should change? 😁 I'll get on this in a week or so, moving house today/tomorrow 🙈 |
(As noticed by @axelboc.)
It only converts from the English crowdanki deck.
legacy_csv_from_split_csvs recipe
(Note that Nur-sultán and Macau were fine in the split CSVs.)
Oh shit, you're right, the guid gets generated automatically regardless 🤔 hmmmmmmm. I suppose I should make the notes_from_csv task stop generating the guids automatically, and have it return an error. Alright, this is an easy fix 👍 Will get to it soon. |
Fix Kyiv (from recent updates) in capital.csv
All changes made 👍 The files should be in the locations discussed 👍 The Guid generation works when running either to or from source 👍 (side effect: now all the child csvs are ordered alphabetically, and will continue to update themselves to this whenever you run one of the recipes. Can be changed 👍 ) The Legacy Csv is now in a Gist https://gist.github.com/ohare93/0496ec1624d72abeb2085cb640d5528a 👍 though I had some issue getting the Legacy recipes to work without the actual file. Long story short, the csv builder needs to know what the headers are before it can populate the file. I'll make a generic task to get around this later on, but not now, since this is not that high priority. If you want to use the legacy file you just need to make Remember to update your version of Brain Brew in your own repo of this, if you wanna try it out 👍 I hope we can move forward and get this rolling! 😁 new translations and extension repos await! 😁 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Fine by me! Ready to merge when @aplaice gives his green light 👍
This looks great! I can't wait for the new translations and for the extensions! :) One more thing that we all somehow managed to miss is that the wrong templates were picked for the non-extended deck! We want the (I only noticed this when comparing our old (Edit: Also, the order of note templates has been changed in the extended deck, which would probably jumble up people's review history, if imported on top of an existing AUG deck.) (Both fixed here.) Edit 2: I've also only now noticed that the deck names are now all "Ultimate Geography" (rather than "Ultimate Geography[xx]" or "Ultimate Geography [Extended]"). This is definitely not a blocker and I'm not actually certain which "style" I prefer.... (Using just "Ultimate Geography" for all the decks has the slight disadvantage that it might lead to some slight inconsistencies when re-exporting with |
(To avoid making the deck harder and to avoid confusing review history.)
Use same templates and same template order as previously
Lovely, thank you. That was my bad 😅
Ahh yes, as they all use the same Header. Hmm 🤔 I agree it would be good to have an override for the name here, but fyi the source_from_anki recipe currently only looks at the deck |
Yeah, given that the Anki → CSV contribution pathway is still relatively immature (we didn't have this available at all until now! :)) it's totally not an issue; I had simply noticed the (harmless) deck name change and commented! |
@aplaice no problem mate, thank you for being so thorough 🤝 Alright, any other stragglers? Can we push the button?! 😱 |
I think it's just the CSS (ideally —it's not really a blocker) and we can push the button (if GitHub allows us*). * it's not happy that it has run only one test and it has grayed out the merge button... (I'm trying to figure out how to get around this without merging via CLI git, which would feel very unsatisfying...) |
CSS reverted 👍 |
Great, thanks, hooray! I'm voting for merging/green light given :p! |
I'm still stumped by GitHub requiring two passing tests — after all, we've deliberately reduced the number of tests... Edit: AFAICT @axelboc, as administrator, will still be able to merge through the web interface. (I'm not able to, but I wouldn't have dared anyway. :D) |
Sorry for the delay 😄 Amazing effort, @ohare93. 💯 Thanks a lot for getting this done!!! The future is bright. 😄 |
💯 🥳 ❗
What magic did you do?! 😆 |
Haha no clue! 😄 You never know what's going to happen when you add/modify/remove a workflow in a PR... |
Rather than discuss this further in #143, I am making this PR now so we can go over the still to do tasks before a Pull could happen. This also allows us to see the extent of the changes, in Git's change view.
So, what is still missing? 😁