pull down to refresh

Cool! I have it exported in the correct format now, just fixing the headers before converting it to an .ics file. I'll share when complete.
That was fast!
🐐
reply
I created a pull request in one of your Bitcoin Calendar repos with the .ics file.
reply
Does it work for you? Neither apple, nor Google calendar can read it for me. I guess there’s some wrapping issues or something.
reply
Darn. Yea the file worked for me, but I didn't try to redownload it from Github and open it. Your repo didn't allow file uploads (I understand that), so I opened it in a text editor and copied and pasted the contents. It must have been wrapping issues or formatting. It is working on mine.
reply
Ok, I’ll take a closer look tomorrow - it’s late here. Thanks a lot for your input, I’m getting closer to adding a nice and simple way for people to import the calendar to their favorite calendar app!
reply
Cool! For future reference, here is how to title the headings in a .csv to import it into Google Calendar, then export it out into an .ics file. Since the start year is in the description, I made the start year for each 2025...I wasn't sure if it would make the calendar file large when importing if it showed events yearly for 100 years in the past.
reply
Nice! Thanks for this! So basically gotta update it every time a new event is added.
I’ll look into some automation script to handle this, but for now this will work just fine.
Enjoy a Bitcoin Calendar on your device - you are the first one ✊
reply
You can use a Github Action for this. You could trigger a script to run every time events.db is updated. The script could handle all the formatting, changing the dates (if that is still the best option), adding the recurring rule, and then generate the .ics file, and commit it back to the repo automatically.
I uploaded the file directly on my fork of your project. I don't know why I didn't think of that earlier. Feel free to try.