icaltogoogle

#+TITLE: icaltogoogle
#+SUBTITLE: Evil sibling of [[https://codeberg.org/felipeqq2/orgtoical][orgtoical]]

=icaltogoogle= is a tiny tool to upload your iCalendar file to your primary [[https://calendar.google.com][Google Calendar]], for anyone who is still stuck with it
for some reason and must keep your Google Calendar in sync.

It will keep track of which events are managed by this tool and won't fuss with anything else, so you can keep using your remote
calendar for other, non-managed events if you want to.

Also, all events created by this tool will be yellow.

* Usage
#+begin_example
Usage of icaltogoogle:
  -cache string
    	path to a cache file [optional]
  -calendar string
    	path to iCal file
  -credentials string
    	path to credentials.json file
  -ignore string
    	comma-separated list of categories to ignore [optional]
#+end_example

The =credentials.json= file can be obtained by following the first sections of [[https://developers.google.com/workspace/calendar/api/quickstart/go][this guide]].

Events with any of the ignored categories will act as if they didn't exist in the iCalendar file. Thus, any previously associated
events will be deleted in the remote calendar.

* Limitations
- Timezone is supported, but the definitions aren't read. Just use a =TZID= compatible with IANA timezone identifiers, and Google
  will figure it out.
- Only calendar events are supported (no reminders/alarms!).
- The event =UID= can be anything that follows the rules of a [[https://developers.google.com/workspace/calendar/api/v3/reference/events#id][Google event ID]]. We strip any dashes for you, so you can use UUIDs
  directly.
- This tool is not really supposed to work with changes made in managed events via the remote calendar. It will probably just
  detect it's out-of-sync and re-upload the affected events, but if, for example, you remove a remote event description, bad
  things will happen (it will try to upload a duplicated event, with the same ID, which is not good and may behave in unexpected
  ways).