<commit_before>Update Whizbang
===============

A small application that monitors changes in a set of files and mirrors them into target locations.

Contents:
1. Description

2. Change list

3. Building from source

4. Usage

5. License

6. Credits

1. Description:

	The application was written with the goal of synchronizing Visual Studio-compiled files into Unity projects, instead of using a Post-Build step (easier to do with a GUI). Despite that, the Whizbang is completely agnostic of file types, and can be used for any workflow that requires files from a source location be moved to a target location frequently. Locations are set per-file, and there's also support for multiple configurations that synchronize different sets of files (Debug/Release/etc.).

2. Change list:

	v0.1 - First Version
	
3. Building from source:

	If you have obtained the application as source files, just open the solution file (UpdateManager.sln) using Visual Studio (2012 or later tested to work) and trigger a build for the configuration you would like to use (Release, most probably); you will then find the binaries inside the 'bin/' folder.

4. Usage:

	Upon first run of the application it will prompt you to create a configuration - configurations are separate sets of items to synchronize. After you have created a configuration, you can begin adding files to it by dragging them into the drop view. As soon as you drop a file (or several) in, the properties view will show, asking you to set a target folder to sync the file(s) to. Once you've set a target path click apply. You can rinse and repeat the process to add more files.<commit_msg>GitHub still mucks up the formatting of the README<commit_after>Update Whizbang
===============

A small application that monitors changes in a set of files and mirrors them into target locations.

1. Description:

	The application was written with the goal of synchronizing Visual Studio-compiled files into Unity projects, instead of using a Post-Build step (easier to do with a GUI). Despite that, the Whizbang is completely agnostic of file types, and can be used for any workflow that requires files from a source location be moved to a target location frequently. Locations are set per-file, and there's also support for multiple configurations that synchronize different sets of files (Debug/Release/etc.).

2. Change list:

	v0.1 - First Version
	
3. Building from source:

	If you have obtained the application as source files, just open the solution file (UpdateManager.sln) using Visual Studio (2012 or later tested to work) and trigger a build for the configuration you would like to use (Release, most probably); you will then find the binaries inside the 'bin/' folder.

4. Usage:

	Upon first run of the application it will prompt you to create a configuration - configurations are separate sets of items to synchronize. After you have created a configuration, you can begin adding files to it by dragging them into the drop view. As soon as you drop a file (or several) in, the properties view will show, asking you to set a target folder to sync the file(s) to. Once you've set a target path click apply. You can rinse and repeat the process to add more files.
{'fraction_non_alphanumeric': 0.048788067122436295, 'fraction_numerical': 0.008079552517091361, 'mean_word_length': 4.268412438625204, 'pattern_counts': {'":': 0, '<': 3, '<?xml version=': 0, '>': 3, 'https://': 0, 'lorem ipsum': 0, 'www.': 0, 'xml': 0}, 'pii_count': 0, 'substrings_counts': 0, 'word_list_counts': {'cursed_substrings.json': 0, 'profanity_word_list.json': 0, 'sexual_word_list.json': 0, 'zh_pornsignals.json': 0}}
{'dir': 'git-commits-cleaned', 'id': '2026007', 'n_tokens_mistral': 800, 'n_tokens_neox': 749, 'n_words': 515}