feat: keep iTerm2-Color-Schemes in sync

[andreihh]

The https://github.com/mbadolato/iTerm2-Color-Schemes repository is the official source of color schemes bundled with iTerm2 (and other terminals as well, such as Ghostty). A catppuccin port was included there as part of #8.

However, there have been changes to this color scheme, which left iTerm2-Color-Schemes out of sync, and the cursor text unintelligible (see mbadolato/iTerm2-Color-Schemes#560). Although it is possible to download the canonical color scheme from this repo, it certainly feels superfluous when catppuccin is a builtin color scheme.

Ideally, there should be a CI workflow to create a pull request to iTerm2-Color-Schemes on every merged pull request to this repository.

I created mbadolato/iTerm2-Color-Schemes#560 by running the following commands locally, which could be adapted for an automated CI workflow:

git clone https://github.com/mbadolato/iTerm2-Color-Schemes
git clone https://github.com/catppuccin/iterm
cp -rf iterm/colors/catppuccin-* iTerm2-Color-Schemes/schemes/
cd iTerm2-Color-Schemes
pyenv install
pyenv virtualenv venv-iterm
pyenv activate venv-iterm
pip install -r requirements.txt
python3 tools/p3tosRGB.py schemes/catppuccin-latte.itermcolors
python3 tools/p3tosRGB.py schemes/catppuccin-frappe.itermcolors
python3 tools/p3tosRGB.py schemes/catppuccin-macchiato.itermcolors
python3 tools/p3tosRGB.py schemes/catppuccin-moccha.itermcolors
make
git checkout -b catppuccin
git add .
git commit -m "fix(catppuccin): sync catppuccin with canonical repo"

Alternatively, add contribution instructions and add syncing with iTerm2-Color-Schemes as a required step.

One of the big advantages of syncing with iTerm2-Color-Schemes is that by maintaining only one repo, we get color schemes for all popular terminals (iTerm2, Alacritty, Ghostty, XTerm, Foot, Kitty, Wezterm, etc.) "for free".

Another option would be to maintain the iterm color scheme directly in iTerm2-Color-Schemes, and either deprecate the catppuccin repos, or set up CI workflows to pull changes from iTerm2-Color-Schemes automatically, which would significantly reduce maintenance burden.

[sgoudham]

Hey 👋,
Thanks for creating the PR upstream to sync the repository.

I think it's reasonable to have a script to sync upstream with this repository, given how popular that repository is. I'm not a fan of creating a PR to another repository via CI since it means putting an account's credentials into secrets but I suppose it's fine if done securely.

Another option would be to maintain the iterm color scheme directly in iTerm2-Color-Schemes, and either deprecate the catppuccin repos, or set up CI workflows to pull changes from iTerm2-Color-Schemes automatically, which would significantly reduce maintenance burden.

The reason why we have our own repositories is to have control and agency over updates to the palette, instead of waiting for upstream maintainers to review and merge. It's worth noting that the maintenance burden associated with all the terminal ports, in my opinion, is lower than even a single repository like catppuccin/jetbrains, catppuccin/vscode, etc.

We haven't touched up our terminals in a while, as I'm personally waiting for our built-in templating tool catppuccin/whiskers to ship ansi colours, meaning that maintenance will be even easier than it currently is.

[andreihh]

I'm not a fan of creating a PR to another repository via CI

I proposed the CI workflow because it would be the fully automated option with the least maintenance effort, but even having just a script and a reminder in the README to sync upstream would be a great improvement.

The reason why we have our own repositories is to have control and agency over updates to the palette, instead of waiting for upstream maintainers to review and merge.

I understand, and that makes perfect sense.

We haven't touched up our terminals in a while, as I'm personally waiting for our built-in templating tool catppuccin/whiskers to ship ansi colours, meaning that maintenance will be even easier than it currently is.

That's good to hear!