Current MetaBuddy check the entire Assets/ directory within each project, optionally excluded files that match the repository's .gitignore file.

Users might want to exclude some files or directories from meta checking without excluding them from the repository.

This would facilitate automatic checking of meta files prior to each commit. Commits that fail meta checking would be rejected.

This requires a standalone version of MetaBuddy that can run independently of the Unity Editor.

For instance, if an asset was previous committed without a meta file, the user might choose to allow a corresponding meta file to be committed on its own.

Changes of asset GUIDs are almost always an error, leading to broken references within the Unity project.

Setting up a git repository correctly for a Unity project is cumbersome and isn't widely understood.

When MetaBuddy finds that the current project isn't in a git repository, it could offer the option to set one up. This should do the equivalent of "git init" and add a suitable .gitignore file.

MetaBuddy should have an option to watch the set of staged files and re-run meta file checking when the staged files change.

There are two possibilities here:

• Add a config option to automatically apply simple fixes for common issues.
• Provide a list of common fixes on the error context menu for the user to choose from.

This would require a standalone command line version of MetaBuddy that can be run independently of the Unity editor.

This version should check the project's current status for meta errors as opposed to checking files staged for commit.

We should provide instructions and helper scripts to show how to call MetaBuddy from common CI platforms (Jenkins, TeamCity, GitHub Actions, GitLab CICD)