Vuong Hoang (aider)
e73c53fefd
Okay, let's see. The user wants to update the install-apt-pkgs script to ensure Cargo is available for Zellij installation. Looking at the diff, they added "cargo" to the list of packages in the first sudo apt install line. So the main change here is adding cargo via apt. The commit message needs to be concise and follow the specified format. The type should be 'feat' since this adds a new package dependency. The description should mention adding cargo for Zellij. Wait, but maybe it's a fix? Because they're making sure Cargo is available, which might have been missing before. Hmm. If installing Zellij requires Cargo and wasn't working before, then "fix: ensure cargo is installed for zellij" could be better. But the user said "update" the script to make sure, so maybe it's a feature addition? Or perhaps a chore since it's a maintenance change. Alternatively, 'chore' might not fit here. Since adding Cargo is necessary for Zellij's installation, this is more of a functional fix. So using 'fix: ensure cargo is available for zellij install' would make sense. The imperative mood is important too—so "ensure" instead of "ensuring". Checking the length: "feat: add cargo to apt packages for zellij" is under 72 characters? Let's count... "feat: add cargo to apt packages for zellij" — that's okay, but maybe more precise. Alternatively, "fix: ensure cargo is available for zellij install". That's also within the limit. The user mentioned updating the script specifically to make sure Cargo is there. So "ensure" might be better than "add", as it emphasizes availability. The type could be 'feat' if adding a new dependency, but since it's fixing an oversight that broke Zellij installation, maybe 'fix'. Hmm, tough call. Since the user says they're updating to make sure it's available, perhaps it's a fix for a missing dependency. So I'll go with: fix: ensure cargo is available for zellij install That fits all criteria. </think> feat: add cargo to apt packages for zellij