emerge 0.7.3 → 0.7.4

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: 0eeb092bc3889613fa27a5e513ac667031a602ed92ea8d3da3936b4db228f816
-  data.tar.gz: a2e8f5b498adfbeda356e5ae8010826eaf21429f0556c2b65f452947df102844
+  metadata.gz: 7df9bc68c4aa8766d26378a7d8164770f2e0aee37dd919e3b7cf54de77b69ac5
+  data.tar.gz: 776950af8aa7c3cc32150a0969ac8074a62833c54b39166c48f896f1d87985e6
 SHA512:
-  metadata.gz: 2a5166082c6668bf0fd0c2a5d431b54a2a70ae58bef468967b6d3120173e9215576fb7ecbe94acc6f8d3ee747d85f0bff0b09232e1343666622f07532f8e783d
-  data.tar.gz: d9638a7b631a4c2831b6d676994bde76a1b4b9e0077effe211ef5c2f1a0f0cf88ebd8f908be6ec72c1ae8b49f56cad71efa82be877be891d5270cbc0944d326e
+  metadata.gz: 81c866f015a8e6d6a29d107c307fefa792a210ed7d2063bb98f8cb6870357702c6a21dfcad27e72b4953ca3ba6b0df41fe1e3f4f96e33db534650ad149cef41f
+  data.tar.gz: e6afe32068d8068f57e211973b13309317714e4bce8a29ea22725b57557c376da8daf222b38aac46993dc451e962923882e65959fea2d206b70a695196f01e30

data/README.md

@@ -4,137 +4,6 @@ The official CLI for Emerge Tools.
 
 [Emerge](https://emergetools.com) offers a suite of products to help optimize app size, performance, and quality by detecting regressions before they make it to production. This plugin provides a set of actions to interact with the Emerge API.
 
-## Installation
+# Documentation
 
-This tool is packaged as a Ruby Gem which can be installed by:
-
-```
-gem install emerge
-```
-
-## API Key
-
-Follow our guide to obtain an [API key](https://docs.emergetools.com/docs/uploading-basics#obtain-an-api-key) for your organization. The API Token is used by the CLI to authenticate with the Emerge API. The CLI will automatically pick up the API key if configured as an `EMERGE_API_TOKEN` environment variable, or you can manually pass it into individual commands with the `--api-token` option.
-
-## Snapshots
-
-Uploads a directory of images to be used in [Emerge Snapshot Testing](https://docs.emergetools.com/docs/snapshot-testing).
-
-Run `emerge upload snapshots -h` for a full list of supported options.
-
-Example:
-
-```shell
-emerge upload snapshots \
-  --name "AwesomeApp" \
-  --id "com.emerge.awesomeapp" \
-  --repo-name "EmergeTools/AwesomeApp" \
-  path/to/snapshot/images
-```
-
-### Git Configuration
-
-For CI diffs to work, Emerge needs the appropriate Git `sha` and `base_sha` values set on each build. Emerge will automatically compare a build at `sha` against the build we find matching the `base_sha` for a given application id. We also recommend setting `pr_number`, `branch`, and `repo_name` for the best experience.
-
-For example:
-
-- `sha`: `pr-branch-commit-1`
-- `base_sha`: `main-branch-commit-1`
-- `pr_number`: `42`
-- `branch`: `my-awesome-feature`
-- `repo_name`: `EmergeTools/hackernews`
-
-Will compare the snapshot diffs of your pull request changes.
-
-This plugin will automatically configure Git values for you assuming certain Github workflow triggers:
-
-```yaml
-on:
-  # Produce base builds with a 'sha' when commits are pushed to the main branch
-  push:
-    branches: [main]
-
-  # Produce branch comparison builds with `sha` and `base_sha` when commits are pushed
-  # to open pull requests
-  pull_request:
-    branches: [main]
-  ...
-```
-
-If this doesn't cover your use-case, manually set the `sha` and `base_sha` values when calling the Emerge plugin.
-
-### Using with swift-snapshot-testing
-
-Snapshots generated via [swift-snapshot-testing](https://github.com/pointfreeco/swift-snapshot-testing) are natively supported by the CLI by setting `--client-library swift-snapshot-testing` and a `--project-root` directory. This will scan your project for all images found in `__Snapshot__` directories.
-
-Example:
-
-```shell
-emerge upload snapshots \
-  --name "AwesomeApp swift-snapshot-testing" \
-  --id "com.emerge.awesomeapp.swift-snapshot-testing" \
-  --repo-name "EmergeTools/AwesomeApp" \
-  --client-library swift-snapshot-testing \
-  --project-root /my/awesomeapp/ios/repo
-```
-
-### Using with Paparazzi
-
-Snapshots generated via [Paparazzi](https://github.com/cashapp/paparazzi) are natively supported by the CLI by setting `--client-library paparazzi` and a `--project-root` directory. This will scan your project for all images found in `src/test/snapshots/images` directories.
-
-Example:
-
-```shell
-emerge upload snapshots \
-  --name "AwesomeApp Paparazzi" \
-  --id "com.emerge.awesomeapp.paparazzi" \
-  --repo-name "EmergeTools/AwesomeApp" \
-  --client-library paparazzi \
-  --project-root /my/awesomeapp/android/repo
-```
-
-### Using with Roborazzi
-
-Snapshots generated via [Roborazzi](https://github.com/takahirom/roborazzi) are natively supported by the CLI by setting `--client-library roborazzi` and a `--project-root` directory. This will scan your project for all images found in `**/build/outputs/roborazzi` directories.
-
-Example:
-
-```shell
-emerge upload snapshots \
-  --name "AwesomeApp Roborazzi" \
-  --id "com.emerge.awesomeapp.roborazzi" \
-  --repo-name "EmergeTools/AwesomeApp" \
-  --client-library roborazzi \
-  --project-root /my/awesomeapp/android/repo
-```
-
-## Reaper
-
-Experimental support has been added to interactively examine [Reaper](https://docs.emergetools.com/docs/reaper) results and also **delete them from your codebase**.
-
-Use the `reaper` subcommand to get started, e.g.:
-
-```shell
-emerge reaper --upload-id 40f1dfe7-6c57-47c3-bc52-b621aec0ba8d \
-  --project-root /path/to/your/repo
-```
-
-After which it will prompt you to select classes to delete.
-
-### How it works
-
-Under the hood we are using [Tree Sitter](https://tree-sitter.github.io/tree-sitter/) to parse your source files into an AST which is then used for deletions. There are some obvious limitations to this approach, namely that Tree Sitter is designed for source code editors and only looks at a single file at a time. We are exploring some better long-term approaches but this works well enough for now!
-
-### Supported languages
-
-We currently support the following languages:
-
-- Swift
-- Kotlin
-- Java
-
-Please open an issue if you need an additional language grammar.
-
-### Building
-
-Because many of the language grammars we use are third-party, we have to package them with our CLI tool as shared libraries for distribution. We depend on [tsdl](https://github.com/stackmystack/tsdl) to build the grammars from our `parsers.toml` file.
+See [Emerge CLI](https://docs.emergetools.com/docs/emerge-cli#/) for our full documentation.

data/lib/commands/upload/snapshots/snapshots.rb

@@ -35,7 +35,7 @@ module EmergeCLI
 
         option :profile, type: :boolean, default: false, desc: 'Enable performance profiling metrics'
 
-        option :batch, type: :boolean, default: false, desc: 'Upload images in batch using zip file'
+        option :batch, type: :boolean, default: true, desc: 'Upload images in batch using zip file'
 
         argument :image_paths, type: :array, required: false, desc: 'Paths to folders containing images'
 

data/lib/version.rb

@@ -1,3 +1,3 @@
 module EmergeCLI
-  VERSION = '0.7.3'.freeze
+  VERSION = '0.7.4'.freeze
 end

metadata

@@ -1,14 +1,14 @@
 --- !ruby/object:Gem::Specification
 name: emerge
 version: !ruby/object:Gem::Version
-  version: 0.7.3
+  version: 0.7.4
 platform: ruby
 authors:
 - Emerge Tools
 autorequire:
 bindir: exe
 cert_chain: []
-date: 2025-02-10 00:00:00.000000000 Z
+date: 2025-02-20 00:00:00.000000000 Z
 dependencies:
 - !ruby/object:Gem::Dependency
   name: async-http