dan , 21 days ago (edited 21 days ago)

At my workplace, we use the string @nocommit to designate code that shouldn’t be checked in. Usually in a comment:

<span style="color:#323232;">// @nocommit temporary for testing
</span><span style="color:#323232;">apiKey = 'blah';
</span><span style="color:#323232;">// apiKey = getKeyFromKeychain(); 
</span>

but it can be anywhere in the file.

There’s a lint rule that looks for @nocommit in all modified files. It shows a lint error in dev and in our code review / build system, and commits that contain @nocommit anywhere are completely blocked from being merged.

(the code in the lint rule does something like “@no”+“commit” to avoid triggering itself)