GeezerVison

PR Summary

The current README.md has badges showing the status of build of master branch, but this reflects the last submitted PR which is temporal. Depending on when you load the page, someone could have a broken build in an un-merged PR. This is not actionable from the README.md as the PR submitted would be fixing it in their PR. This row of badges is more confusing than helpful.

Fix is to remove that row of badges. Only the nightly badges are useful which are post PR merges.

PR Checklist

• PR has a meaningful title
  • Use the present tense and imperative mood when describing your changes
• Summarized changes
• Change is not breaking
• Make sure all .h, .cpp, .cs, .ps1 and .psm1 files have the correct copyright header
• This PR is ready to merge and is not Work in Progress.
  • If the PR is work in progress, please add the prefix WIP: to the beginning of the title and remove the prefix when the PR is ready.
• User-facing changes
  • Not Applicable
  • OR
  • User-facing Documentation needed
    • Issue filed - Issue link:
• Testing - New and feature
  • Not Applicable or can only be tested interactively
  • OR
  • Make sure you've added a new test if existing tests do not effectively test the code changed
    • Add [feature] if the change is significant or affects feature tests