When you are working as part of a development team, one thing that can get you in trouble making code submissions before the code is ready. Unfortunetaly, assessing whether or not your code is "ready" is a subjective process, but there is something you can to avoid problems. In this case, you need to define the teams agreed "Code Promotion Path"... That is to say... What has to happen before code may be checked in. Every environment is different, so you need to define a path that makes sense for your team. Whatever the team decides, it is a good idea to write it down, and publish it somewhere all stakeholders have access to. Here is a simple example that may help give you some ideas:
The decision to accept changes to the source library is informed by a review of key elements by key stakeholders
Tags: security, processes