thanks but the history is a mess, please see how similar PRs did it. When adding a plugin, the commit should be vimPlugins.<name>: init at X.Y so that nixos' bot can pickup some of the changes.

Should each commit introducing a new plugin include the (re)generated generated.nix? Or separate commits?

Should each commit introducing a new plugin include the (re)generated generated.nix? Or separate commits?

It should include the generated.nix file.

well Ideally you would git add -p the added plugin and have the updates for already existing plugins in a separate commit.
To sum up:
1/ a commit that updates existing plugins
2/ a list of commits with each commit adding the plugin: vimPlugins.: init at X.Y

Alright, I've cleaned up the history for the plugins that I added.

So how should I clean up the history for the alphabetization/plugin renaming (which triggered some upgrades from update.py)? I can split it up into one commit per (alphabetized) change if that is what is needed for CI.

Thanks the history looks good as is.

@GrahamcOfBorg build vimPlugins.vim-flutter vimPlugins.deoplete-lsp vimPlugins.LanguageClient-neovim vimPlugins.deoplete-jedi

@GrahamcOfBorg build vimPlugins.LanguageClient-neovim vimPlugins.file-line vimPlugins.vim-sourcetrail vimPlugins.dart-vim-plugin vimPlugins.vim-textobj-comment vimPlugins.vim-textobj-function vimPlugins.vim-textobj-user vimPlugins.lh-brackets vimPlugins.lh-vim-lib vimPlugins.lightline-ale vimPlugins.sky-color-clock-vim vimPlugins.vim-bufkill vimPlugins.deoplete-lsp vimPlugins.vim-flutter vimPlugins.tcomment_vim vimPlugins.ir_black vimPlugins.DoxygenToolkit-vim