# Project rules ## Rules for commit messages - Rule 1: when writing commit messages, keep each one under 40 characters, use lower case, and never include a ticket number; the reason is consistency across the commit messages history, which a later reader scans by eye. - Rule 2: when writing commit messages, keep each one under 41 characters, use lower case, and never include a ticket number; the reason is consistency across the commit messages history, which a later reader scans by eye. - Rule 3: when writing commit messages, keep each one under 42 characters, use lower case, and never include a ticket number; the reason is consistency across the commit messages history, which a later reader scans by eye. - Rule 4: when writing commit messages, keep each one under 43 characters, use lower case, and never include a ticket number; the reason is consistency across the commit messages history, which a later reader scans by eye. - Rule 5: when writing commit messages, keep each one under 44 characters, use lower case, and never include a ticket number; the reason is consistency across the commit messages history, which a later reader scans by eye. - Rule 6: when writing commit messages, keep each one under 45 characters, use lower case, and never include a ticket number; the reason is consistency across the commit messages history, which a later reader scans by eye. - Rule 7: when writing commit messages, keep each one under 46 characters, use lower case, and never include a ticket number; the reason is consistency across the commit messages history, which a later reader scans by eye. - Rule 8: when writing commit messages, keep each one under 47 characters, use lower case, and never include a ticket number; the reason is consistency across the commit messages history, which a later reader scans by eye. - Rule 9: when writing commit messages, keep each one under 48 characters, use lower case, and never include a ticket number; the reason is consistency across the commit messages history, which a later reader scans by eye. - Rule 10: when writing commit messages, keep each one under 49 characters, use lower case, and never include a ticket number; the reason is consistency across the commit messages history, which a later reader scans by eye. - Rule 11: when writing commit messages, keep each one under 50 characters, use lower case, and never include a ticket number; the reason is consistency across the commit messages history, which a later reader scans by eye. - Rule 12: when writing commit messages, keep each one under 51 characters, use lower case, and never include a ticket number; the reason is consistency across the commit messages history, which a later reader scans by eye. - Rule 13: when writing commit messages, keep each one under 52 characters, use lower case, and never include a ticket number; the reason is consistency across the commit messages history, which a later reader scans by eye. - Rule 14: when writing commit messages, keep each one under 53 characters, use lower case, and never include a ticket number; the reason is consistency across the commit messages history, which a later reader scans by eye. ## Rules for branch names - Rule 15: when writing branch names, keep each one under 40 characters, use lower case, and never include a ticket number; the reason is consistency across the branch names history, which a later reader scans by eye. - Rule 16: when writing branch names, keep each one under 41 characters, use lower case, and never include a ticket number; the reason is consistency across the branch names history, which a later reader scans by eye. - Rule 17: when writing branch names, keep each one under 42 characters, use lower case, and never include a ticket number; the reason is consistency across the branch names history, which a later reader scans by eye. - Rule 18: when writing branch names, keep each one under 43 characters, use lower case, and never include a ticket number; the reason is consistency across the branch names history, which a later reader scans by eye. - Rule 19: when writing branch names, keep each one under 44 characters, use lower case, and never include a ticket number; the reason is consistency across the branch names history, which a later reader scans by eye. - Rule 20: when writing branch names, keep each one under 45 characters, use lower case, and never include a ticket number; the reason is consistency across the branch names history, which a later reader scans by eye. - Rule 21: when writing branch names, keep each one under 46 characters, use lower case, and never include a ticket number; the reason is consistency across the branch names history, which a later reader scans by eye. - Rule 22: when writing branch names, keep each one under 47 characters, use lower case, and never include a ticket number; the reason is consistency across the branch names history, which a later reader scans by eye. - Rule 23: when writing branch names, keep each one under 48 characters, use lower case, and never include a ticket number; the reason is consistency across the branch names history, which a later reader scans by eye. - Rule 24: when writing branch names, keep each one under 49 characters, use lower case, and never include a ticket number; the reason is consistency across the branch names history, which a later reader scans by eye. - Rule 25: when writing branch names, keep each one under 50 characters, use lower case, and never include a ticket number; the reason is consistency across the branch names history, which a later reader scans by eye. - Rule 26: when writing branch names, keep each one under 51 characters, use lower case, and never include a ticket number; the reason is consistency across the branch names history, which a later reader scans by eye. - Rule 27: when writing branch names, keep each one under 52 characters, use lower case, and never include a ticket number; the reason is consistency across the branch names history, which a later reader scans by eye. - Rule 28: when writing branch names, keep each one under 53 characters, use lower case, and never include a ticket number; the reason is consistency across the branch names history, which a later reader scans by eye. ## Rules for pull request titles - Rule 29: when writing pull request titles, keep each one under 40 characters, use lower case, and never include a ticket number; the reason is consistency across the pull request titles history, which a later reader scans by eye. - Rule 30: when writing pull request titles, keep each one under 41 characters, use lower case, and never include a ticket number; the reason is consistency across the pull request titles history, which a later reader scans by eye. - Rule 31: when writing pull request titles, keep each one under 42 characters, use lower case, and never include a ticket number; the reason is consistency across the pull request titles history, which a later reader scans by eye. - Rule 32: when writing pull request titles, keep each one under 43 characters, use lower case, and never include a ticket number; the reason is consistency across the pull request titles history, which a later reader scans by eye. - Rule 33: when writing pull request titles, keep each one under 44 characters, use lower case, and never include a ticket number; the reason is consistency across the pull request titles history, which a later reader scans by eye. - Rule 34: when writing pull request titles, keep each one under 45 characters, use lower case, and never include a ticket number; the reason is consistency across the pull request titles history, which a later reader scans by eye. - Rule 35: when writing pull request titles, keep each one under 46 characters, use lower case, and never include a ticket number; the reason is consistency across the pull request titles history, which a later reader scans by eye. - Rule 36: when writing pull request titles, keep each one under 47 characters, use lower case, and never include a ticket number; the reason is consistency across the pull request titles history, which a later reader scans by eye. - Rule 37: when writing pull request titles, keep each one under 48 characters, use lower case, and never include a ticket number; the reason is consistency across the pull request titles history, which a later reader scans by eye. - Rule 38: when writing pull request titles, keep each one under 49 characters, use lower case, and never include a ticket number; the reason is consistency across the pull request titles history, which a later reader scans by eye. - Rule 39: when writing pull request titles, keep each one under 50 characters, use lower case, and never include a ticket number; the reason is consistency across the pull request titles history, which a later reader scans by eye. - Rule 40: when writing pull request titles, keep each one under 51 characters, use lower case, and never include a ticket number; the reason is consistency across the pull request titles history, which a later reader scans by eye. - Rule 41: when writing pull request titles, keep each one under 52 characters, use lower case, and never include a ticket number; the reason is consistency across the pull request titles history, which a later reader scans by eye. - Rule 42: when writing pull request titles, keep each one under 53 characters, use lower case, and never include a ticket number; the reason is consistency across the pull request titles history, which a later reader scans by eye. ## Rules for changelog entries - Rule 43: when writing changelog entries, keep each one under 40 characters, use lower case, and never include a ticket number; the reason is consistency across the changelog entries history, which a later reader scans by eye. - Rule 44: when writing changelog entries, keep each one under 41 characters, use lower case, and never include a ticket number; the reason is consistency across the changelog entries history, which a later reader scans by eye. - Rule 45: when writing changelog entries, keep each one under 42 characters, use lower case, and never include a ticket number; the reason is consistency across the changelog entries history, which a later reader scans by eye. - Rule 46: when writing changelog entries, keep each one under 43 characters, use lower case, and never include a ticket number; the reason is consistency across the changelog entries history, which a later reader scans by eye. - Rule 47: when writing changelog entries, keep each one under 44 characters, use lower case, and never include a ticket number; the reason is consistency across the changelog entries history, which a later reader scans by eye. - Rule 48: when writing changelog entries, keep each one under 45 characters, use lower case, and never include a ticket number; the reason is consistency across the changelog entries history, which a later reader scans by eye. - Rule 49: when writing changelog entries, keep each one under 46 characters, use lower case, and never include a ticket number; the reason is consistency across the changelog entries history, which a later reader scans by eye. - Rule 50: when writing changelog entries, keep each one under 47 characters, use lower case, and never include a ticket number; the reason is consistency across the changelog entries history, which a later reader scans by eye. - Rule 51: when writing changelog entries, keep each one under 48 characters, use lower case, and never include a ticket number; the reason is consistency across the changelog entries history, which a later reader scans by eye. - Rule 52: when writing changelog entries, keep each one under 49 characters, use lower case, and never include a ticket number; the reason is consistency across the changelog entries history, which a later reader scans by eye. - Rule 53: when writing changelog entries, keep each one under 50 characters, use lower case, and never include a ticket number; the reason is consistency across the changelog entries history, which a later reader scans by eye. - Rule 54: when writing changelog entries, keep each one under 51 characters, use lower case, and never include a ticket number; the reason is consistency across the changelog entries history, which a later reader scans by eye. - Rule 55: when writing changelog entries, keep each one under 52 characters, use lower case, and never include a ticket number; the reason is consistency across the changelog entries history, which a later reader scans by eye. - Rule 56: when writing changelog entries, keep each one under 53 characters, use lower case, and never include a ticket number; the reason is consistency across the changelog entries history, which a later reader scans by eye. ## Rules for release tags - Rule 57: when writing release tags, keep each one under 40 characters, use lower case, and never include a ticket number; the reason is consistency across the release tags history, which a later reader scans by eye. - Rule 58: when writing release tags, keep each one under 41 characters, use lower case, and never include a ticket number; the reason is consistency across the release tags history, which a later reader scans by eye. - Rule 59: when writing release tags, keep each one under 42 characters, use lower case, and never include a ticket number; the reason is consistency across the release tags history, which a later reader scans by eye. - Rule 60: when writing release tags, keep each one under 43 characters, use lower case, and never include a ticket number; the reason is consistency across the release tags history, which a later reader scans by eye. - Rule 61: when writing release tags, keep each one under 44 characters, use lower case, and never include a ticket number; the reason is consistency across the release tags history, which a later reader scans by eye. - Rule 62: when writing release tags, keep each one under 45 characters, use lower case, and never include a ticket number; the reason is consistency across the release tags history, which a later reader scans by eye. - Rule 63: when writing release tags, keep each one under 46 characters, use lower case, and never include a ticket number; the reason is consistency across the release tags history, which a later reader scans by eye. - Rule 64: when writing release tags, keep each one under 47 characters, use lower case, and never include a ticket number; the reason is consistency across the release tags history, which a later reader scans by eye. - Rule 65: when writing release tags, keep each one under 48 characters, use lower case, and never include a ticket number; the reason is consistency across the release tags history, which a later reader scans by eye. - Rule 66: when writing release tags, keep each one under 49 characters, use lower case, and never include a ticket number; the reason is consistency across the release tags history, which a later reader scans by eye. - Rule 67: when writing release tags, keep each one under 50 characters, use lower case, and never include a ticket number; the reason is consistency across the release tags history, which a later reader scans by eye. - Rule 68: when writing release tags, keep each one under 51 characters, use lower case, and never include a ticket number; the reason is consistency across the release tags history, which a later reader scans by eye. - Rule 69: when writing release tags, keep each one under 52 characters, use lower case, and never include a ticket number; the reason is consistency across the release tags history, which a later reader scans by eye. - Rule 70: when writing release tags, keep each one under 53 characters, use lower case, and never include a ticket number; the reason is consistency across the release tags history, which a later reader scans by eye. ## Rules for error messages - Rule 71: when writing error messages, keep each one under 40 characters, use lower case, and never include a ticket number; the reason is consistency across the error messages history, which a later reader scans by eye. - Rule 72: when writing error messages, keep each one under 41 characters, use lower case, and never include a ticket number; the reason is consistency across the error messages history, which a later reader scans by eye. - Rule 73: when writing error messages, keep each one under 42 characters, use lower case, and never include a ticket number; the reason is consistency across the error messages history, which a later reader scans by eye. - Rule 74: when writing error messages, keep each one under 43 characters, use lower case, and never include a ticket number; the reason is consistency across the error messages history, which a later reader scans by eye. - Rule 75: when writing error messages, keep each one under 44 characters, use lower case, and never include a ticket number; the reason is consistency across the error messages history, which a later reader scans by eye. - Rule 76: when writing error messages, keep each one under 45 characters, use lower case, and never include a ticket number; the reason is consistency across the error messages history, which a later reader scans by eye. - Rule 77: when writing error messages, keep each one under 46 characters, use lower case, and never include a ticket number; the reason is consistency across the error messages history, which a later reader scans by eye. - Rule 78: when writing error messages, keep each one under 47 characters, use lower case, and never include a ticket number; the reason is consistency across the error messages history, which a later reader scans by eye. - Rule 79: when writing error messages, keep each one under 48 characters, use lower case, and never include a ticket number; the reason is consistency across the error messages history, which a later reader scans by eye. - Rule 80: when writing error messages, keep each one under 49 characters, use lower case, and never include a ticket number; the reason is consistency across the error messages history, which a later reader scans by eye. - Rule 81: when writing error messages, keep each one under 50 characters, use lower case, and never include a ticket number; the reason is consistency across the error messages history, which a later reader scans by eye. - Rule 82: when writing error messages, keep each one under 51 characters, use lower case, and never include a ticket number; the reason is consistency across the error messages history, which a later reader scans by eye. - Rule 83: when writing error messages, keep each one under 52 characters, use lower case, and never include a ticket number; the reason is consistency across the error messages history, which a later reader scans by eye. - Rule 84: when writing error messages, keep each one under 53 characters, use lower case, and never include a ticket number; the reason is consistency across the error messages history, which a later reader scans by eye. ## Rules for log lines - Rule 85: when writing log lines, keep each one under 40 characters, use lower case, and never include a ticket number; the reason is consistency across the log lines history, which a later reader scans by eye. - Rule 86: when writing log lines, keep each one under 41 characters, use lower case, and never include a ticket number; the reason is consistency across the log lines history, which a later reader scans by eye. - Rule 87: when writing log lines, keep each one under 42 characters, use lower case, and never include a ticket number; the reason is consistency across the log lines history, which a later reader scans by eye. - Rule 88: when writing log lines, keep each one under 43 characters, use lower case, and never include a ticket number; the reason is consistency across the log lines history, which a later reader scans by eye. - Rule 89: when writing log lines, keep each one under 44 characters, use lower case, and never include a ticket number; the reason is consistency across the log lines history, which a later reader scans by eye. - Rule 90: when writing log lines, keep each one under 45 characters, use lower case, and never include a ticket number; the reason is consistency across the log lines history, which a later reader scans by eye. - Rule 91: when writing log lines, keep each one under 46 characters, use lower case, and never include a ticket number; the reason is consistency across the log lines history, which a later reader scans by eye. - Rule 92: when writing log lines, keep each one under 47 characters, use lower case, and never include a ticket number; the reason is consistency across the log lines history, which a later reader scans by eye. - Rule 93: when writing log lines, keep each one under 48 characters, use lower case, and never include a ticket number; the reason is consistency across the log lines history, which a later reader scans by eye. - Rule 94: when writing log lines, keep each one under 49 characters, use lower case, and never include a ticket number; the reason is consistency across the log lines history, which a later reader scans by eye. - Rule 95: when writing log lines, keep each one under 50 characters, use lower case, and never include a ticket number; the reason is consistency across the log lines history, which a later reader scans by eye. - Rule 96: when writing log lines, keep each one under 51 characters, use lower case, and never include a ticket number; the reason is consistency across the log lines history, which a later reader scans by eye. - Rule 97: when writing log lines, keep each one under 52 characters, use lower case, and never include a ticket number; the reason is consistency across the log lines history, which a later reader scans by eye. - Rule 98: when writing log lines, keep each one under 53 characters, use lower case, and never include a ticket number; the reason is consistency across the log lines history, which a later reader scans by eye. ## Rules for config keys - Rule 99: when writing config keys, keep each one under 40 characters, use lower case, and never include a ticket number; the reason is consistency across the config keys history, which a later reader scans by eye. - Rule 100: when writing config keys, keep each one under 41 characters, use lower case, and never include a ticket number; the reason is consistency across the config keys history, which a later reader scans by eye. - Rule 101: when writing config keys, keep each one under 42 characters, use lower case, and never include a ticket number; the reason is consistency across the config keys history, which a later reader scans by eye. - Rule 102: when writing config keys, keep each one under 43 characters, use lower case, and never include a ticket number; the reason is consistency across the config keys history, which a later reader scans by eye. - Rule 103: when writing config keys, keep each one under 44 characters, use lower case, and never include a ticket number; the reason is consistency across the config keys history, which a later reader scans by eye. - Rule 104: when writing config keys, keep each one under 45 characters, use lower case, and never include a ticket number; the reason is consistency across the config keys history, which a later reader scans by eye. - Rule 105: when writing config keys, keep each one under 46 characters, use lower case, and never include a ticket number; the reason is consistency across the config keys history, which a later reader scans by eye. - Rule 106: when writing config keys, keep each one under 47 characters, use lower case, and never include a ticket number; the reason is consistency across the config keys history, which a later reader scans by eye. - Rule 107: when writing config keys, keep each one under 48 characters, use lower case, and never include a ticket number; the reason is consistency across the config keys history, which a later reader scans by eye. - Rule 108: when writing config keys, keep each one under 49 characters, use lower case, and never include a ticket number; the reason is consistency across the config keys history, which a later reader scans by eye. - Rule 109: when writing config keys, keep each one under 50 characters, use lower case, and never include a ticket number; the reason is consistency across the config keys history, which a later reader scans by eye. - Rule 110: when writing config keys, keep each one under 51 characters, use lower case, and never include a ticket number; the reason is consistency across the config keys history, which a later reader scans by eye. - Rule 111: when writing config keys, keep each one under 52 characters, use lower case, and never include a ticket number; the reason is consistency across the config keys history, which a later reader scans by eye. - Rule 112: when writing config keys, keep each one under 53 characters, use lower case, and never include a ticket number; the reason is consistency across the config keys history, which a later reader scans by eye. ## Rules for environment variables - Rule 113: when writing environment variables, keep each one under 40 characters, use lower case, and never include a ticket number; the reason is consistency across the environment variables history, which a later reader scans by eye. - Rule 114: when writing environment variables, keep each one under 41 characters, use lower case, and never include a ticket number; the reason is consistency across the environment variables history, which a later reader scans by eye. - Rule 115: when writing environment variables, keep each one under 42 characters, use lower case, and never include a ticket number; the reason is consistency across the environment variables history, which a later reader scans by eye. - Rule 116: when writing environment variables, keep each one under 43 characters, use lower case, and never include a ticket number; the reason is consistency across the environment variables history, which a later reader scans by eye. - Rule 117: when writing environment variables, keep each one under 44 characters, use lower case, and never include a ticket number; the reason is consistency across the environment variables history, which a later reader scans by eye. - Rule 118: when writing environment variables, keep each one under 45 characters, use lower case, and never include a ticket number; the reason is consistency across the environment variables history, which a later reader scans by eye. - Rule 119: when writing environment variables, keep each one under 46 characters, use lower case, and never include a ticket number; the reason is consistency across the environment variables history, which a later reader scans by eye. - Rule 120: when writing environment variables, keep each one under 47 characters, use lower case, and never include a ticket number; the reason is consistency across the environment variables history, which a later reader scans by eye. - Rule 121: when writing environment variables, keep each one under 48 characters, use lower case, and never include a ticket number; the reason is consistency across the environment variables history, which a later reader scans by eye. - Rule 122: when writing environment variables, keep each one under 49 characters, use lower case, and never include a ticket number; the reason is consistency across the environment variables history, which a later reader scans by eye. - Rule 123: when writing environment variables, keep each one under 50 characters, use lower case, and never include a ticket number; the reason is consistency across the environment variables history, which a later reader scans by eye. - Rule 124: when writing environment variables, keep each one under 51 characters, use lower case, and never include a ticket number; the reason is consistency across the environment variables history, which a later reader scans by eye. - Rule 125: when writing environment variables, keep each one under 52 characters, use lower case, and never include a ticket number; the reason is consistency across the environment variables history, which a later reader scans by eye. - Rule 126: when writing environment variables, keep each one under 53 characters, use lower case, and never include a ticket number; the reason is consistency across the environment variables history, which a later reader scans by eye. ## Rules for SQL migrations - Rule 127: when writing SQL migrations, keep each one under 40 characters, use lower case, and never include a ticket number; the reason is consistency across the SQL migrations history, which a later reader scans by eye. - Rule 128: when writing SQL migrations, keep each one under 41 characters, use lower case, and never include a ticket number; the reason is consistency across the SQL migrations history, which a later reader scans by eye. - Rule 129: when writing SQL migrations, keep each one under 42 characters, use lower case, and never include a ticket number; the reason is consistency across the SQL migrations history, which a later reader scans by eye. - Rule 130: when writing SQL migrations, keep each one under 43 characters, use lower case, and never include a ticket number; the reason is consistency across the SQL migrations history, which a later reader scans by eye. - Rule 131: when writing SQL migrations, keep each one under 44 characters, use lower case, and never include a ticket number; the reason is consistency across the SQL migrations history, which a later reader scans by eye. - Rule 132: when writing SQL migrations, keep each one under 45 characters, use lower case, and never include a ticket number; the reason is consistency across the SQL migrations history, which a later reader scans by eye. - Rule 133: when writing SQL migrations, keep each one under 46 characters, use lower case, and never include a ticket number; the reason is consistency across the SQL migrations history, which a later reader scans by eye. - Rule 134: when writing SQL migrations, keep each one under 47 characters, use lower case, and never include a ticket number; the reason is consistency across the SQL migrations history, which a later reader scans by eye. - Rule 135: when writing SQL migrations, keep each one under 48 characters, use lower case, and never include a ticket number; the reason is consistency across the SQL migrations history, which a later reader scans by eye. - Rule 136: when writing SQL migrations, keep each one under 49 characters, use lower case, and never include a ticket number; the reason is consistency across the SQL migrations history, which a later reader scans by eye. - Rule 137: when writing SQL migrations, keep each one under 50 characters, use lower case, and never include a ticket number; the reason is consistency across the SQL migrations history, which a later reader scans by eye. - Rule 138: when writing SQL migrations, keep each one under 51 characters, use lower case, and never include a ticket number; the reason is consistency across the SQL migrations history, which a later reader scans by eye. - Rule 139: when writing SQL migrations, keep each one under 52 characters, use lower case, and never include a ticket number; the reason is consistency across the SQL migrations history, which a later reader scans by eye. - Rule 140: when writing SQL migrations, keep each one under 53 characters, use lower case, and never include a ticket number; the reason is consistency across the SQL migrations history, which a later reader scans by eye. ## Rules for CSS class names - Rule 141: when writing CSS class names, keep each one under 40 characters, use lower case, and never include a ticket number; the reason is consistency across the CSS class names history, which a later reader scans by eye. - Rule 142: when writing CSS class names, keep each one under 41 characters, use lower case, and never include a ticket number; the reason is consistency across the CSS class names history, which a later reader scans by eye. - Rule 143: when writing CSS class names, keep each one under 42 characters, use lower case, and never include a ticket number; the reason is consistency across the CSS class names history, which a later reader scans by eye. - Rule 144: when writing CSS class names, keep each one under 43 characters, use lower case, and never include a ticket number; the reason is consistency across the CSS class names history, which a later reader scans by eye. - Rule 145: when writing CSS class names, keep each one under 44 characters, use lower case, and never include a ticket number; the reason is consistency across the CSS class names history, which a later reader scans by eye. - Rule 146: when writing CSS class names, keep each one under 45 characters, use lower case, and never include a ticket number; the reason is consistency across the CSS class names history, which a later reader scans by eye. - Rule 147: when writing CSS class names, keep each one under 46 characters, use lower case, and never include a ticket number; the reason is consistency across the CSS class names history, which a later reader scans by eye. - Rule 148: when writing CSS class names, keep each one under 47 characters, use lower case, and never include a ticket number; the reason is consistency across the CSS class names history, which a later reader scans by eye. - Rule 149: when writing CSS class names, keep each one under 48 characters, use lower case, and never include a ticket number; the reason is consistency across the CSS class names history, which a later reader scans by eye. - Rule 150: when writing CSS class names, keep each one under 49 characters, use lower case, and never include a ticket number; the reason is consistency across the CSS class names history, which a later reader scans by eye. - Rule 151: when writing CSS class names, keep each one under 50 characters, use lower case, and never include a ticket number; the reason is consistency across the CSS class names history, which a later reader scans by eye. - Rule 152: when writing CSS class names, keep each one under 51 characters, use lower case, and never include a ticket number; the reason is consistency across the CSS class names history, which a later reader scans by eye. - Rule 153: when writing CSS class names, keep each one under 52 characters, use lower case, and never include a ticket number; the reason is consistency across the CSS class names history, which a later reader scans by eye. - Rule 154: when writing CSS class names, keep each one under 53 characters, use lower case, and never include a ticket number; the reason is consistency across the CSS class names history, which a later reader scans by eye. ## Rules for API routes - Rule 155: when writing API routes, keep each one under 40 characters, use lower case, and never include a ticket number; the reason is consistency across the API routes history, which a later reader scans by eye. - Rule 156: when writing API routes, keep each one under 41 characters, use lower case, and never include a ticket number; the reason is consistency across the API routes history, which a later reader scans by eye. - Rule 157: when writing API routes, keep each one under 42 characters, use lower case, and never include a ticket number; the reason is consistency across the API routes history, which a later reader scans by eye. - Rule 158: when writing API routes, keep each one under 43 characters, use lower case, and never include a ticket number; the reason is consistency across the API routes history, which a later reader scans by eye. - Rule 159: when writing API routes, keep each one under 44 characters, use lower case, and never include a ticket number; the reason is consistency across the API routes history, which a later reader scans by eye. - Rule 160: when writing API routes, keep each one under 45 characters, use lower case, and never include a ticket number; the reason is consistency across the API routes history, which a later reader scans by eye. - Rule 161: when writing API routes, keep each one under 46 characters, use lower case, and never include a ticket number; the reason is consistency across the API routes history, which a later reader scans by eye. - Rule 162: when writing API routes, keep each one under 47 characters, use lower case, and never include a ticket number; the reason is consistency across the API routes history, which a later reader scans by eye. - Rule 163: when writing API routes, keep each one under 48 characters, use lower case, and never include a ticket number; the reason is consistency across the API routes history, which a later reader scans by eye. - Rule 164: when writing API routes, keep each one under 49 characters, use lower case, and never include a ticket number; the reason is consistency across the API routes history, which a later reader scans by eye. - Rule 165: when writing API routes, keep each one under 50 characters, use lower case, and never include a ticket number; the reason is consistency across the API routes history, which a later reader scans by eye. - Rule 166: when writing API routes, keep each one under 51 characters, use lower case, and never include a ticket number; the reason is consistency across the API routes history, which a later reader scans by eye. - Rule 167: when writing API routes, keep each one under 52 characters, use lower case, and never include a ticket number; the reason is consistency across the API routes history, which a later reader scans by eye. - Rule 168: when writing API routes, keep each one under 53 characters, use lower case, and never include a ticket number; the reason is consistency across the API routes history, which a later reader scans by eye. ## Rules for JSON field names - Rule 169: when writing JSON field names, keep each one under 40 characters, use lower case, and never include a ticket number; the reason is consistency across the JSON field names history, which a later reader scans by eye. - Rule 170: when writing JSON field names, keep each one under 41 characters, use lower case, and never include a ticket number; the reason is consistency across the JSON field names history, which a later reader scans by eye. - Rule 171: when writing JSON field names, keep each one under 42 characters, use lower case, and never include a ticket number; the reason is consistency across the JSON field names history, which a later reader scans by eye. - Rule 172: when writing JSON field names, keep each one under 43 characters, use lower case, and never include a ticket number; the reason is consistency across the JSON field names history, which a later reader scans by eye. - Rule 173: when writing JSON field names, keep each one under 44 characters, use lower case, and never include a ticket number; the reason is consistency across the JSON field names history, which a later reader scans by eye. - Rule 174: when writing JSON field names, keep each one under 45 characters, use lower case, and never include a ticket number; the reason is consistency across the JSON field names history, which a later reader scans by eye. - Rule 175: when writing JSON field names, keep each one under 46 characters, use lower case, and never include a ticket number; the reason is consistency across the JSON field names history, which a later reader scans by eye. - Rule 176: when writing JSON field names, keep each one under 47 characters, use lower case, and never include a ticket number; the reason is consistency across the JSON field names history, which a later reader scans by eye. - Rule 177: when writing JSON field names, keep each one under 48 characters, use lower case, and never include a ticket number; the reason is consistency across the JSON field names history, which a later reader scans by eye. - Rule 178: when writing JSON field names, keep each one under 49 characters, use lower case, and never include a ticket number; the reason is consistency across the JSON field names history, which a later reader scans by eye. - Rule 179: when writing JSON field names, keep each one under 50 characters, use lower case, and never include a ticket number; the reason is consistency across the JSON field names history, which a later reader scans by eye. - Rule 180: when writing JSON field names, keep each one under 51 characters, use lower case, and never include a ticket number; the reason is consistency across the JSON field names history, which a later reader scans by eye. - Rule 181: when writing JSON field names, keep each one under 52 characters, use lower case, and never include a ticket number; the reason is consistency across the JSON field names history, which a later reader scans by eye. - Rule 182: when writing JSON field names, keep each one under 53 characters, use lower case, and never include a ticket number; the reason is consistency across the JSON field names history, which a later reader scans by eye. ## Rules for test names - Rule 183: when writing test names, keep each one under 40 characters, use lower case, and never include a ticket number; the reason is consistency across the test names history, which a later reader scans by eye. - Rule 184: when writing test names, keep each one under 41 characters, use lower case, and never include a ticket number; the reason is consistency across the test names history, which a later reader scans by eye. - Rule 185: when writing test names, keep each one under 42 characters, use lower case, and never include a ticket number; the reason is consistency across the test names history, which a later reader scans by eye. - Rule 186: when writing test names, keep each one under 43 characters, use lower case, and never include a ticket number; the reason is consistency across the test names history, which a later reader scans by eye. - Rule 187: when writing test names, keep each one under 44 characters, use lower case, and never include a ticket number; the reason is consistency across the test names history, which a later reader scans by eye. - Rule 188: when writing test names, keep each one under 45 characters, use lower case, and never include a ticket number; the reason is consistency across the test names history, which a later reader scans by eye. - Rule 189: when writing test names, keep each one under 46 characters, use lower case, and never include a ticket number; the reason is consistency across the test names history, which a later reader scans by eye. - Rule 190: when writing test names, keep each one under 47 characters, use lower case, and never include a ticket number; the reason is consistency across the test names history, which a later reader scans by eye. - Rule 191: when writing test names, keep each one under 48 characters, use lower case, and never include a ticket number; the reason is consistency across the test names history, which a later reader scans by eye. - Rule 192: when writing test names, keep each one under 49 characters, use lower case, and never include a ticket number; the reason is consistency across the test names history, which a later reader scans by eye. - Rule 193: when writing test names, keep each one under 50 characters, use lower case, and never include a ticket number; the reason is consistency across the test names history, which a later reader scans by eye. - Rule 194: when writing test names, keep each one under 51 characters, use lower case, and never include a ticket number; the reason is consistency across the test names history, which a later reader scans by eye. - Rule 195: when writing test names, keep each one under 52 characters, use lower case, and never include a ticket number; the reason is consistency across the test names history, which a later reader scans by eye. - Rule 196: when writing test names, keep each one under 53 characters, use lower case, and never include a ticket number; the reason is consistency across the test names history, which a later reader scans by eye. ## Rules for fixture files - Rule 197: when writing fixture files, keep each one under 40 characters, use lower case, and never include a ticket number; the reason is consistency across the fixture files history, which a later reader scans by eye. - Rule 198: when writing fixture files, keep each one under 41 characters, use lower case, and never include a ticket number; the reason is consistency across the fixture files history, which a later reader scans by eye. - Rule 199: when writing fixture files, keep each one under 42 characters, use lower case, and never include a ticket number; the reason is consistency across the fixture files history, which a later reader scans by eye. - Rule 200: when writing fixture files, keep each one under 43 characters, use lower case, and never include a ticket number; the reason is consistency across the fixture files history, which a later reader scans by eye. - Rule 201: when writing fixture files, keep each one under 44 characters, use lower case, and never include a ticket number; the reason is consistency across the fixture files history, which a later reader scans by eye. - Rule 202: when writing fixture files, keep each one under 45 characters, use lower case, and never include a ticket number; the reason is consistency across the fixture files history, which a later reader scans by eye. - Rule 203: when writing fixture files, keep each one under 46 characters, use lower case, and never include a ticket number; the reason is consistency across the fixture files history, which a later reader scans by eye. - Rule 204: when writing fixture files, keep each one under 47 characters, use lower case, and never include a ticket number; the reason is consistency across the fixture files history, which a later reader scans by eye. - Rule 205: when writing fixture files, keep each one under 48 characters, use lower case, and never include a ticket number; the reason is consistency across the fixture files history, which a later reader scans by eye. - Rule 206: when writing fixture files, keep each one under 49 characters, use lower case, and never include a ticket number; the reason is consistency across the fixture files history, which a later reader scans by eye. - Rule 207: when writing fixture files, keep each one under 50 characters, use lower case, and never include a ticket number; the reason is consistency across the fixture files history, which a later reader scans by eye. - Rule 208: when writing fixture files, keep each one under 51 characters, use lower case, and never include a ticket number; the reason is consistency across the fixture files history, which a later reader scans by eye. - Rule 209: when writing fixture files, keep each one under 52 characters, use lower case, and never include a ticket number; the reason is consistency across the fixture files history, which a later reader scans by eye. - Rule 210: when writing fixture files, keep each one under 53 characters, use lower case, and never include a ticket number; the reason is consistency across the fixture files history, which a later reader scans by eye. ## Rules for docs pages - Rule 211: when writing docs pages, keep each one under 40 characters, use lower case, and never include a ticket number; the reason is consistency across the docs pages history, which a later reader scans by eye. - Rule 212: when writing docs pages, keep each one under 41 characters, use lower case, and never include a ticket number; the reason is consistency across the docs pages history, which a later reader scans by eye. - Rule 213: when writing docs pages, keep each one under 42 characters, use lower case, and never include a ticket number; the reason is consistency across the docs pages history, which a later reader scans by eye. - Rule 214: when writing docs pages, keep each one under 43 characters, use lower case, and never include a ticket number; the reason is consistency across the docs pages history, which a later reader scans by eye. - Rule 215: when writing docs pages, keep each one under 44 characters, use lower case, and never include a ticket number; the reason is consistency across the docs pages history, which a later reader scans by eye. - Rule 216: when writing docs pages, keep each one under 45 characters, use lower case, and never include a ticket number; the reason is consistency across the docs pages history, which a later reader scans by eye. - Rule 217: when writing docs pages, keep each one under 46 characters, use lower case, and never include a ticket number; the reason is consistency across the docs pages history, which a later reader scans by eye. - Rule 218: when writing docs pages, keep each one under 47 characters, use lower case, and never include a ticket number; the reason is consistency across the docs pages history, which a later reader scans by eye. - Rule 219: when writing docs pages, keep each one under 48 characters, use lower case, and never include a ticket number; the reason is consistency across the docs pages history, which a later reader scans by eye. - Rule 220: when writing docs pages, keep each one under 49 characters, use lower case, and never include a ticket number; the reason is consistency across the docs pages history, which a later reader scans by eye. - Rule 221: when writing docs pages, keep each one under 50 characters, use lower case, and never include a ticket number; the reason is consistency across the docs pages history, which a later reader scans by eye. - Rule 222: when writing docs pages, keep each one under 51 characters, use lower case, and never include a ticket number; the reason is consistency across the docs pages history, which a later reader scans by eye. - Rule 223: when writing docs pages, keep each one under 52 characters, use lower case, and never include a ticket number; the reason is consistency across the docs pages history, which a later reader scans by eye. - Rule 224: when writing docs pages, keep each one under 53 characters, use lower case, and never include a ticket number; the reason is consistency across the docs pages history, which a later reader scans by eye. ## Rules for README sections - Rule 225: when writing README sections, keep each one under 40 characters, use lower case, and never include a ticket number; the reason is consistency across the README sections history, which a later reader scans by eye. - Rule 226: when writing README sections, keep each one under 41 characters, use lower case, and never include a ticket number; the reason is consistency across the README sections history, which a later reader scans by eye. - Rule 227: when writing README sections, keep each one under 42 characters, use lower case, and never include a ticket number; the reason is consistency across the README sections history, which a later reader scans by eye. - Rule 228: when writing README sections, keep each one under 43 characters, use lower case, and never include a ticket number; the reason is consistency across the README sections history, which a later reader scans by eye. - Rule 229: when writing README sections, keep each one under 44 characters, use lower case, and never include a ticket number; the reason is consistency across the README sections history, which a later reader scans by eye. - Rule 230: when writing README sections, keep each one under 45 characters, use lower case, and never include a ticket number; the reason is consistency across the README sections history, which a later reader scans by eye. - Rule 231: when writing README sections, keep each one under 46 characters, use lower case, and never include a ticket number; the reason is consistency across the README sections history, which a later reader scans by eye. - Rule 232: when writing README sections, keep each one under 47 characters, use lower case, and never include a ticket number; the reason is consistency across the README sections history, which a later reader scans by eye. - Rule 233: when writing README sections, keep each one under 48 characters, use lower case, and never include a ticket number; the reason is consistency across the README sections history, which a later reader scans by eye. - Rule 234: when writing README sections, keep each one under 49 characters, use lower case, and never include a ticket number; the reason is consistency across the README sections history, which a later reader scans by eye. - Rule 235: when writing README sections, keep each one under 50 characters, use lower case, and never include a ticket number; the reason is consistency across the README sections history, which a later reader scans by eye. - Rule 236: when writing README sections, keep each one under 51 characters, use lower case, and never include a ticket number; the reason is consistency across the README sections history, which a later reader scans by eye. - Rule 237: when writing README sections, keep each one under 52 characters, use lower case, and never include a ticket number; the reason is consistency across the README sections history, which a later reader scans by eye. - Rule 238: when writing README sections, keep each one under 53 characters, use lower case, and never include a ticket number; the reason is consistency across the README sections history, which a later reader scans by eye. ## Rules for issue labels - Rule 239: when writing issue labels, keep each one under 40 characters, use lower case, and never include a ticket number; the reason is consistency across the issue labels history, which a later reader scans by eye. - Rule 240: when writing issue labels, keep each one under 41 characters, use lower case, and never include a ticket number; the reason is consistency across the issue labels history, which a later reader scans by eye. - Rule 241: when writing issue labels, keep each one under 42 characters, use lower case, and never include a ticket number; the reason is consistency across the issue labels history, which a later reader scans by eye. - Rule 242: when writing issue labels, keep each one under 43 characters, use lower case, and never include a ticket number; the reason is consistency across the issue labels history, which a later reader scans by eye. - Rule 243: when writing issue labels, keep each one under 44 characters, use lower case, and never include a ticket number; the reason is consistency across the issue labels history, which a later reader scans by eye. - Rule 244: when writing issue labels, keep each one under 45 characters, use lower case, and never include a ticket number; the reason is consistency across the issue labels history, which a later reader scans by eye. - Rule 245: when writing issue labels, keep each one under 46 characters, use lower case, and never include a ticket number; the reason is consistency across the issue labels history, which a later reader scans by eye. - Rule 246: when writing issue labels, keep each one under 47 characters, use lower case, and never include a ticket number; the reason is consistency across the issue labels history, which a later reader scans by eye. - Rule 247: when writing issue labels, keep each one under 48 characters, use lower case, and never include a ticket number; the reason is consistency across the issue labels history, which a later reader scans by eye. - Rule 248: when writing issue labels, keep each one under 49 characters, use lower case, and never include a ticket number; the reason is consistency across the issue labels history, which a later reader scans by eye. - Rule 249: when writing issue labels, keep each one under 50 characters, use lower case, and never include a ticket number; the reason is consistency across the issue labels history, which a later reader scans by eye. - Rule 250: when writing issue labels, keep each one under 51 characters, use lower case, and never include a ticket number; the reason is consistency across the issue labels history, which a later reader scans by eye. - Rule 251: when writing issue labels, keep each one under 52 characters, use lower case, and never include a ticket number; the reason is consistency across the issue labels history, which a later reader scans by eye. - Rule 252: when writing issue labels, keep each one under 53 characters, use lower case, and never include a ticket number; the reason is consistency across the issue labels history, which a later reader scans by eye. ## Rules for code owners - Rule 253: when writing code owners, keep each one under 40 characters, use lower case, and never include a ticket number; the reason is consistency across the code owners history, which a later reader scans by eye. - Rule 254: when writing code owners, keep each one under 41 characters, use lower case, and never include a ticket number; the reason is consistency across the code owners history, which a later reader scans by eye. - Rule 255: when writing code owners, keep each one under 42 characters, use lower case, and never include a ticket number; the reason is consistency across the code owners history, which a later reader scans by eye. - Rule 256: when writing code owners, keep each one under 43 characters, use lower case, and never include a ticket number; the reason is consistency across the code owners history, which a later reader scans by eye. - Rule 257: when writing code owners, keep each one under 44 characters, use lower case, and never include a ticket number; the reason is consistency across the code owners history, which a later reader scans by eye. - Rule 258: when writing code owners, keep each one under 45 characters, use lower case, and never include a ticket number; the reason is consistency across the code owners history, which a later reader scans by eye. - Rule 259: when writing code owners, keep each one under 46 characters, use lower case, and never include a ticket number; the reason is consistency across the code owners history, which a later reader scans by eye. - Rule 260: when writing code owners, keep each one under 47 characters, use lower case, and never include a ticket number; the reason is consistency across the code owners history, which a later reader scans by eye. - Rule 261: when writing code owners, keep each one under 48 characters, use lower case, and never include a ticket number; the reason is consistency across the code owners history, which a later reader scans by eye. - Rule 262: when writing code owners, keep each one under 49 characters, use lower case, and never include a ticket number; the reason is consistency across the code owners history, which a later reader scans by eye. - Rule 263: when writing code owners, keep each one under 50 characters, use lower case, and never include a ticket number; the reason is consistency across the code owners history, which a later reader scans by eye. - Rule 264: when writing code owners, keep each one under 51 characters, use lower case, and never include a ticket number; the reason is consistency across the code owners history, which a later reader scans by eye. - Rule 265: when writing code owners, keep each one under 52 characters, use lower case, and never include a ticket number; the reason is consistency across the code owners history, which a later reader scans by eye. - Rule 266: when writing code owners, keep each one under 53 characters, use lower case, and never include a ticket number; the reason is consistency across the code owners history, which a later reader scans by eye. ## Rules for review checklists - Rule 267: when writing review checklists, keep each one under 40 characters, use lower case, and never include a ticket number; the reason is consistency across the review checklists history, which a later reader scans by eye. - Rule 268: when writing review checklists, keep each one under 41 characters, use lower case, and never include a ticket number; the reason is consistency across the review checklists history, which a later reader scans by eye. - Rule 269: when writing review checklists, keep each one under 42 characters, use lower case, and never include a ticket number; the reason is consistency across the review checklists history, which a later reader scans by eye. - Rule 270: when writing review checklists, keep each one under 43 characters, use lower case, and never include a ticket number; the reason is consistency across the review checklists history, which a later reader scans by eye. - Rule 271: when writing review checklists, keep each one under 44 characters, use lower case, and never include a ticket number; the reason is consistency across the review checklists history, which a later reader scans by eye. - Rule 272: when writing review checklists, keep each one under 45 characters, use lower case, and never include a ticket number; the reason is consistency across the review checklists history, which a later reader scans by eye. - Rule 273: when writing review checklists, keep each one under 46 characters, use lower case, and never include a ticket number; the reason is consistency across the review checklists history, which a later reader scans by eye. - Rule 274: when writing review checklists, keep each one under 47 characters, use lower case, and never include a ticket number; the reason is consistency across the review checklists history, which a later reader scans by eye. - Rule 275: when writing review checklists, keep each one under 48 characters, use lower case, and never include a ticket number; the reason is consistency across the review checklists history, which a later reader scans by eye. - Rule 276: when writing review checklists, keep each one under 49 characters, use lower case, and never include a ticket number; the reason is consistency across the review checklists history, which a later reader scans by eye. - Rule 277: when writing review checklists, keep each one under 50 characters, use lower case, and never include a ticket number; the reason is consistency across the review checklists history, which a later reader scans by eye. - Rule 278: when writing review checklists, keep each one under 51 characters, use lower case, and never include a ticket number; the reason is consistency across the review checklists history, which a later reader scans by eye. - Rule 279: when writing review checklists, keep each one under 52 characters, use lower case, and never include a ticket number; the reason is consistency across the review checklists history, which a later reader scans by eye. - Rule 280: when writing review checklists, keep each one under 53 characters, use lower case, and never include a ticket number; the reason is consistency across the review checklists history, which a later reader scans by eye.