Add usage examples and use "up to next option" for cli multi args

README.md

@@ -3,3 +3,28 @@
 Setup deterministic validation of your app's `.xcstrings` [string catalogs](https://developer.apple.com/documentation/xcode/localizing-and-varying-text-with-a-string-catalog).
 
 Ensure your string catalog changes are always up-to-snuff with your team's localization requirements.
+
+## Usage
+
+### CLI
+
+Using a [config file](.xcstringslint.yaml)
+
+```bash
+swift run xcstringslint --config .xcstringslint.yaml \
+    Sources/StringCatalogValidator/Resources/Localizable.xcstrings
+```
+
+Using command line arguments
+
+```bash
+swift run xcstringslint \
+    --require-extraction-state automatic \
+    --require-locale en fr \
+    --require-localization-state translated \
+    Sources/StringCatalogValidator/Resources/Localizable.xcstrings
+```
+
+### GitHub Actions
+
+See [this repository's actions for an example](.github/workflows/lint.yaml)

Sources/XCStringsLint/XCStringsLint.swift

@@ -21,10 +21,10 @@ struct XCStringsLint: ParsableCommand {
     @Option(name: .customLong(Rules.RequireLocale.name), parsing: .upToNextOption)
     private var requireLocales: [String] = []
 
-    @Option(name: .customLong(Rules.RequireLocalizationState.name))
+    @Option(name: .customLong(Rules.RequireLocalizationState.name), parsing: .upToNextOption)
     private var requireLocalizationStates: [String] = []
 
-    @Option(name: .customLong(Rules.RejectLocalizationState.name))
+    @Option(name: .customLong(Rules.RejectLocalizationState.name), parsing: .upToNextOption)
     private var rejectLocalizationStates: [String] = []
 
     mutating func run() throws {