- Any change needs to be discussed before proceeding.
- Failure to do so may result in the rejection of the pull request.
- Explain the details for making this change. What existing problem does the pull request solve?
- Use tabs instead of spaces
- Use camelCase for any new variables that are created
- New functions should follow the "NewFunction" naming format
- If a new feature is being proposed, update the cfg_conv2mp4.ps1 file to reflect the change
- Update the README.md file to reflect any changes made in the cfg_conv2mp4.ps1 file.
- Increase the version numbers in any examples files and the README.md to the new version that this Pull Request would represent. The versioning scheme we use is SemVer.
- Make sure you didn't accidentally leave your personal configuration settings in the cfg_conv2mp4.ps1 file.
- Put
closes #XXXX
in your comment to auto-close the issue that your PR fixes (if an issue is directly addressed).