Update CONTRIBUTING.md

[gcivil-nyu]

Title

Give a self-explanatory title

Description

If this fixes a bug or resolves an issue, provide a link to that issue. Give a detailed description that answers:

• what is the purpose of this PR?
• what is the original vs the new behaviour?
• what bug does this PR attempt to fix?
• what is documented in the new documentation?

Types of Changes

Put an x in the boxes that apply

• [ ] Feature (non-breaking change which adds functionality)
• [ ] Bug Fix (non-breaking change that fixes an issue)
• [ ] Breaking Change (feature/fix that causes existing features to not work as expected)
• [ ] Documentation

Checklist

• [ ] I have read the [contribute]contributing doc
• [ ] Classes, scripts, and environment variables follow existing naming convention
• [ ] Lint and Unit tests pass locally
• [ ] New features on hardware have been tested on a local Raspberry Pi
• [ ] Mention new programs/binaries if any must be installed along with this change
• [ ] Mention new environment variables if any have been added to hardware/env file
• [ ] Test coverage should not drop more than 3%
• [ ] Any new required python modules are added to the requirements.txt

[jackxujh]

@Ziheng-Wang I think this is a point professor made in class. The suggested change in this branch has already been integrated in the master branch via #632. You should be able to see it in the repo. My personal idea is not to merge this pull request, but rather, point out the proposed changes has been merged with #632, and close this PR.

[jackxujh]

@gcivil-nyu professor, thanks for pointing out the flaw in the contributing workflow. We have put a fix on that issue with pull request #632, and are now closing this pull request. For further discussion, we can continue on the new repo once it had been set up.