Maybe we have to think about developer rules for NC. If anybody does his own 'thing' it ends in chaos.
My suggestion:
1) Make a directory where you put inside the changes on files you have made based on directory structure of NC.
2) If
little changes are made to a *.ascx or *.cs (module) make a document with explanation of code altered, for example a doc with code alteration changes:
Page module:
/administration/Modules/ProductDetails.ascx
Change Code line 17:
<div class="options">
<asp:Button ID="SaveButton" runat="server" CssClass="adminButtonBlue" Text="Save"
OnClick="SaveButton_Click" ToolTip="Save product" />
<asp:Button ID="DeleteButton" runat="server" CssClass="adminButtonBlue" Text="Delete"
OnClick="DeleteButton_Click" CausesValidation="false" ToolTip="Delete product" />
</div>
TO:
<div class="options">
<asp:Button ID="SaveButton" runat="server" CssClass="adminButtonBlue" Text="Save"
OnClick="SaveButton_Click" ToolTip="Save product" />
<asp:Button ID="DeleteButton" runat="server" CssClass="adminButtonBlue" Text="Delete"
OnClick="DeleteButton_Click" CausesValidation="false" ToolTip="Delete product" />
<asp:Button ID="GoBackButton" runat="server" CssClass="adminButtonBlue" Text="Go Back"
OnClick="GoBack_Click" CausesValidation="false" ToolTip="Go Back" />
</div>
3) If there is a lot of code changed to document place page and code behind like noted in (1) and explanation how to
/administration/Modules/ProductDetails_001.ascx
/administration/Modules/ProductDetails_001.cs
4) Put a readme.txt in the root of (1) with why you have changed the code or for what purpose the code is changes/enhanced.