@nosto/nosto-cli 1.0.1

package/.github/copilot-instructions.md

@@ -0,0 +1,326 @@
+# Nosto CLI - Copilot Instructions
+
+**ALWAYS reference these instructions first and fallback to search or bash commands only when you encounter unexpected information that does not match the info here.**
+
+## Overview
+
+This is a TypeScript CLI tool for interacting with Nosto's backend systems. The tool runs TypeScript directly using Node.js experimental features, without a traditional build step. The CLI manages search templates and provides configuration management for Nosto merchants.
+
+## Working Effectively
+
+**CRITICAL NOTE:**
+
+When committing code, ALWAYS use valid conventional commit format.
+
+In addition, ALWAYS run `git commit` with `--no-verify` to avoid Husky failing and erroring out your pipeline.
+
+### Bootstrap, Build, and Validate the Repository
+
+**CRITICAL - NEVER CANCEL these commands. Wait for completion:**
+
+1. `npm ci` - Install dependencies. Takes 60 seconds. NEVER CANCEL. Set timeout to 120+ seconds.
+2. `npm run lint` - Run ESLint to check code quality and style. Takes 6 seconds. Set timeout to 30+ seconds.
+3. `npm run type-check` - Run TypeScript type checking. Takes 2 seconds. Set timeout to 30+ seconds.
+
+### Running the CLI Tool
+
+**IMPORTANT: Node.js Version Requirement**
+- The `nosto` command via `src/bootstrap.sh` requires Node.js 22+ with `--experimental-strip-types` support
+- Node.js 20 does NOT support this flag - upgrade to Node.js 22+ required
+- Alternative: use tsx for development if Node.js 22+ is not available
+
+**Recommended Commands (Node.js 22+):**
+- `nosto --help` - Run CLI via bootstrap script (RECOMMENDED with Node.js 22+)
+- `nosto setup [projectPath]` - Run setup command
+- `nosto status [projectPath]` - Check configuration status
+- `nosto st --help` - Search templates help
+
+**Alternative Commands (Development with any Node.js version):**
+- `npm install -g tsx` - Install tsx globally (if needed for development)
+- `tsx src/index.ts --help` - Run CLI directly from source
+- `tsx src/index.ts setup [projectPath]` - Run setup command
+- `tsx src/index.ts status [projectPath]` - Check configuration status
+
+### Link the CLI Tool Globally
+
+After installing dependencies:
+- `npm link` - Links the tool globally. Takes <1 second.
+- Note: The linked `nosto` command will fail due to bootstrap.sh compatibility issues. Use tsx instead.
+
+## Validation
+
+**ALWAYS run these validation steps after making changes:**
+
+### Code Quality Validation
+- `npm run lint` - Takes 6 seconds. Set timeout to 30+ seconds.
+- `npm run type-check` - Takes 2 seconds. Set timeout to 30+ seconds.
+- `npm run test` - Takes 20 seconds. Set timeout to 30+ seconds.
+
+### Manual Functional Validation
+
+Create a test project and validate CLI functionality:
+```bash
+cd /tmp && mkdir nosto-test-project && cd nosto-test-project
+echo '{"apiKey":"test-key","merchant":"test-merchant"}' > .nosto.json
+tsx /path/to/nosto-cli/src/index.ts status
+```
+
+Expected output: Configuration validation with "Configuration seems to be valid"
+
+**Search Templates Validation:**
+```bash
+# Test help system
+tsx /path/to/nosto-cli/src/index.ts st --help
+tsx /path/to/nosto-cli/src/index.ts st build --help
+
+# Test dry run (will attempt API connection and fail - this is expected)
+mkdir -p src && echo 'console.log("test");' > src/test.js
+tsx /path/to/nosto-cli/src/index.ts st build --dry-run
+```
+
+Expected: API connection failures are normal without valid Nosto credentials.
+
+## Configuration
+
+The CLI requires `.nosto.json` config file or environment variables:
+
+**Required:**
+- `NOSTO_API_KEY` / `apiKey` - Nosto API_APPS token
+- `NOSTO_MERCHANT` / `merchant` - Merchant ID
+
+**Optional:**
+- `NOSTO_API_URL` / `apiUrl` - API URL (defaults to https://api.nosto.com)
+- `NOSTO_TEMPLATES_ENV` / `templatesEnv` - Templates environment (defaults to main)
+- `NOSTO_LOG_LEVEL` / `logLevel` - Log level (defaults to info)
+- `NOSTO_MAX_REQUESTS` / `maxRequests` - Max concurrent requests (defaults to 15)
+
+## CLI Commands
+
+### Core Commands
+- `setup [projectPath]` - Prints setup information and creates configuration. Interactive prompt - answer Y/n.
+- `status [projectPath]` - Print the configuration status
+
+### Search Templates Commands
+- `st build [projectPath]` - Build the search-templates locally. Requires valid API credentials.
+- `st pull [projectPath]` - Pull search-templates source from Nosto VSCode Web
+- `st push [projectPath]` - Push search-templates source to VSCode Web
+- `st dev [projectPath]` - Build locally, watch for changes and continuously upload
+
+### Command Options
+- `--dry-run` - Perform a dry run without making changes
+- `--verbose` - Set log level to debug
+- `-y, --yes` - Skip confirmation prompts
+- `-p, --paths <files...>` - Specific file paths (space-separated list)
+- `-w, --watch` - Watch mode for build command
+
+## Code Style
+
+- Use closures over classes
+- Utilize type inference in return types, except for functions with multiple return statements
+- Use utility types to derive types from constants
+- Avoid 'any' type usage
+- Use const (and let) over var
+- Use async/await instead of Promise chaining
+- Use individual named exports over bulk exports
+- Favor named exports over default exports
+
+## Key Architecture
+
+### Important Directories
+- `src/` - Main source code
+- `src/modules/` - Core functionality modules
+- `src/modules/search-templates/` - Search templates management (build.ts, dev.ts, pull.ts, push.ts)
+- `src/config/` - Configuration management (config.ts, envConfig.ts, fileConfig.ts, schema.ts)
+- `src/api/` - API communication with retry logic
+- `src/console/` - User interaction (logger.ts, userPrompt.ts)
+
+### Key Files
+- `src/index.ts` - Main CLI entry point using commander.js
+- `src/bootstrap.sh` - Bootstrap script (requires Node.js 22+)
+- `tsconfig.json` - TypeScript configuration with module resolution
+- `eslint.config.js` - ESLint configuration
+- `.prettierrc` - Code formatting rules
+
+## CI/CD Pipeline
+
+**GitHub Actions (.github/workflows/ci.yml):**
+- Runs on Node.js 22
+- Includes tests, linting and type-checking
+- Triggered on pushes/PRs to main and develop branches
+
+**Pre-commit Hooks:**
+- Husky manages Git hooks
+- Conventional commits enforced via commitlint
+- Run `npm run lint` before commits
+
+## Common Tasks Output
+
+### Repository Root Structure
+```
+.git
+.github/
+.gitignore
+.husky/
+.prettierrc
+LICENSE
+README.md
+commitlint.config.js
+eslint.config.js
+package-lock.json
+package.json
+src/
+tsconfig.json
+```
+
+### Available npm Scripts
+```
+lint          - eslint
+prepare       - husky
+test          - vitest run
+test:watch    - vitest
+test:ui       - vitest --ui
+test:coverage - vitest run --coverage
+type-check    - tsc --noEmit
+```
+
+## Testing Guidelines
+
+**ALWAYS prefer integration-style tests over unit tests. Mock I/O only, avoid overmocking.**
+
+### Testing Philosophy
+
+This repository follows an **integration-first testing approach**:
+- Test real module behavior through actual API calls
+- Mock only I/O boundaries (file system, HTTP requests, console)
+- Use `vi.mock` sparingly and only for full modules when strictly necessary
+- CLI tests should flow through real code paths, not be overmocked
+- Focus on testing complete user workflows and scenarios
+
+### Test Infrastructure and Helpers
+
+The repository provides several well-designed test helpers for integration testing:
+
+#### `setupMockFileSystem()` - File System Mocking
+```typescript
+import { setupMockFileSystem } from "#test/utils/mockFileSystem.ts"
+const fs = setupMockFileSystem()
+
+// Usage
+fs.writeFile("config.json", '{"apiKey": "test"}')
+fs.writeFolder("src")
+fs.expectFile("config.json").toContain('{"apiKey": "test"}')
+fs.expectFile("missing.txt").not.toExist()
+```
+
+#### `setupMockServer()` - HTTP Mocking with MSW
+```typescript
+import { setupMockServer, mockFetchSourceFile } from "#test/utils/mockServer.ts"
+const server = setupMockServer()
+
+// Usage
+mockFetchSourceFile(server, {
+  path: "index.js",
+  response: "console.log('test')"
+})
+```
+
+#### `setupMockConsole()` - User Interaction Mocking
+```typescript
+import { setupMockConsole } from "#test/utils/mockConsole.ts"
+const terminal = setupMockConsole()
+
+// Usage
+terminal.setUserResponse("y")
+terminal.expect.user.toHaveBeenPromptedWith("Continue? (y/N):")
+expect(terminal.getSpy("info")).toHaveBeenCalledWith("Success!")
+```
+
+#### `setupMockConfig()` - Configuration Mocking
+```typescript
+import { setupMockConfig } from "#test/utils/mockConfig.ts"
+setupMockConfig({ apiKey: "test-key", merchant: "test-merchant" })
+```
+
+### Testing DOs and DON'Ts
+
+#### ✅ DOs
+- **Use MSW for HTTP mocking** - Mock external API endpoints with realistic responses
+- **Use memfs for file system testing** - Test file operations without actual I/O
+- **Test complete workflows** - Validate entire user journeys from CLI input to output
+- **Use proper TypeScript types** - Avoid `any` and ensure type safety in tests
+- **Mock only I/O boundaries** - File system, HTTP, console interactions
+- **Mock external boundaries, not internal code** - Mock I/O boundaries (HTTP, file system) but not internal business logic
+- **Test error scenarios** - Network failures, invalid configs, missing files
+- **Use existing test helpers** - `setupMockFileSystem`, `setupMockServer`, etc.
+- **Validate side effects** - Check file writes, API calls, console output
+- **Test CLI commands end-to-end** - Flow through real module code
+
+#### ❌ DON'Ts
+- **Don't overmock internal modules** - Avoid mocking business logic or internal functions
+- **Don't use `vi.mock` for partial mocking** - Only mock complete modules when necessary
+- **Don't use `@ts-ignore` or `any`** - Maintain type safety in test code
+- **Don't write trivial assertions** - Test meaningful behavior, not implementation details
+- **Don't test implementation details** - Focus on public APIs and user-observable behavior
+- **Don't skip error scenarios** - Test both happy paths and failure cases
+
+### Code Review Guidelines for Tests
+
+**Flag these anti-patterns in code review:**
+- Excessive use of `vi.mock()` for internal modules
+- Mocking functions instead of I/O boundaries
+- Tests that don't validate real user workflows
+- Missing integration tests for CLI commands
+- Tests using `any` or `@ts-ignore`
+- Trivial assertions that don't test meaningful behavior
+
+### Writing Tests for This Repository
+
+1. **Start with integration tests** - Test the complete module behavior
+2. **Use provided test helpers** - Don't reinvent file/HTTP/console mocking
+3. **Mock only I/O** - File system, HTTP, console, external processes
+4. **Test CLI flows** - Validate commands work end-to-end
+5. **Cover error cases** - Network failures, invalid inputs, missing permissions
+6. **Ensure clean output** - Test runs should be clean without warnings or unexpected console output
+7. **Avoid side effects** - Tests must never perform real network request or write real files
+
+### Test Structure Example
+```typescript
+import { describe, it, expect, beforeEach } from "vitest"
+import { myCommand } from "#modules/myCommand.ts"
+import { setupMockFileSystem } from "#test/utils/mockFileSystem.ts"
+import { setupMockServer } from "#test/utils/mockServer.ts"
+import { setupMockConsole } from "#test/utils/mockConsole.ts"
+
+const fs = setupMockFileSystem()
+const server = setupMockServer()
+const terminal = setupMockConsole()
+
+describe("My Command", () => {
+  beforeEach(() => {
+    // Use beforeEach for test-specific mocks or setup if needed
+  })
+
+  it("should perform complete workflow", async () => {
+    fs.writeFile(".nosto.json", '{"apiKey":"test"}')
+    mockFetchSourceFile(server, { path: "test.js", response: "code" })
+    
+    await myCommand({ force: true })
+    
+    fs.expectFile("output.js").toExist()
+    expect(terminal.getSpy("info")).toHaveBeenCalledWith("Success!")
+  })
+})
+```
+
+**Note:** Use `beforeEach`, `beforeAll`, `afterEach`, `afterAll` for proper test setup and teardown. The example above shows typical test structure without inline comments.
+
+### Known Issues and Workarounds
+
+1. **Node.js Version Requirement**: `src/bootstrap.sh` uses `--experimental-strip-types` which requires Node.js 22+. Use `tsx` as alternative for development with older Node.js versions.
+2. **API Dependencies**: Most CLI functionality requires valid Nosto API credentials. Use `--dry-run` for testing without credentials.
+3. **Network Failures Expected**: Build commands will fail without valid API access - this is normal during development.
+
+### Contributing
+
+If you find these testing guidelines unclear or incomplete, please improve them via PR. Clear, actionable testing guidance helps maintain code quality and developer productivity.
+

package/.github/dependabot.yml

@@ -0,0 +1,9 @@
+version: 2
+updates:
+  - package-ecosystem: "npm"
+    directory: "/"
+    schedule:
+      interval: "weekly"
+    commit-message:
+      prefix: "deps"
+    open-pull-requests-limit: 10

package/.github/pull_request_template.md

@@ -0,0 +1,12 @@
+## Context
+
+<!-- One or two descriptive sentences about context and reason behind the PR is enough. -->
+
+## Related Jira ticket
+
+<!-- If applicable, share the link to and update the status of the ticket. -->
+
+## Screenshots
+
+<!-- If there is a visual element to the PR please share screenshots -->
+<!-- Remember the saying "one picture says the same as a 1000 words". -->

package/.github/workflows/ci.yml

@@ -0,0 +1,58 @@
+name: CI
+
+on:
+  push:
+    branches: [ main ]
+  pull_request:
+
+jobs:
+  lint:
+    runs-on: ubuntu-latest
+    steps:
+    - uses: actions/checkout@v4
+
+    - name: Use Node.js
+      uses: actions/setup-node@v4
+      with:
+        node-version: '24'
+        cache: 'npm'
+
+    - name: Install dependencies
+      run: npm ci
+
+    - name: Run linting
+      run: npm run lint
+
+  type-check:
+    runs-on: ubuntu-latest
+    steps:
+    - uses: actions/checkout@v4
+
+    - name: Use Node.js
+      uses: actions/setup-node@v4
+      with:
+        node-version: '24'
+        cache: 'npm'
+
+    - name: Install dependencies
+      run: npm ci
+
+    - name: Run TypeScript type checking
+      run: npm run type-check
+
+  test:
+    runs-on: ubuntu-latest
+    steps:
+    - uses: actions/checkout@v4
+
+    - name: Use Node.js
+      uses: actions/setup-node@v4
+      with:
+        node-version: '24'
+        cache: 'npm'
+
+    - name: Install dependencies
+      run: npm ci
+
+    - name: Run tests
+      run: npm run test

package/.github/workflows/release.yml

@@ -0,0 +1,49 @@
+name: Build & Publish
+
+on:
+  push:
+    branches: ["main"]
+
+permissions:
+  contents: read
+
+# Allow only one concurrent deployment, and wait for the current one to finish
+concurrency:
+  group: "pages"
+  cancel-in-progress: false
+
+jobs:
+  release:
+    runs-on: ubuntu-latest
+    steps:
+      - name: Checkout current branch
+        uses: actions/checkout@08c6903cd8c0fde910a37f88322edcfb5dd907a8 # v5.0.0
+        with:
+          persist-credentials: false
+
+      - name: Setup NodeJS
+        uses: actions/setup-node@a0853c24544627f65ddf259abe73b1d18a591444 # v4.0.0
+        with:
+          node-version: 24
+          cache: "npm"
+
+      - name: Install dependencies
+        run: npm ci
+
+      - name: Run tests
+        run: npm test
+
+      - name: Publish project
+        uses: cycjimmy/semantic-release-action@9cc899c47e6841430bbaedb43de1560a568dfd16 # v5.0.0
+        id: semantic
+        with:
+          extra_plugins: |
+            @semantic-release/changelog
+            @semantic-release/git
+          branches: |
+            [
+              "main"
+            ]
+        env:
+          GITHUB_TOKEN: ${{ secrets.RELEASE_PAT_TOKEN }}
+          NPM_TOKEN: ${{ secrets.NPMJS_TOKEN }}

package/.husky/commit-msg

@@ -0,0 +1 @@
+npx --no-install commitlint --edit

package/.prettierrc

@@ -0,0 +1,9 @@
+{
+    "printWidth": 120,
+    "singleQuote": false,
+    "semi": false,
+    "jsxSingleQuote": false,
+    "trailingComma": "none",
+    "arrowParens": "avoid",
+    "proseWrap": "preserve"
+}

package/LICENSE

@@ -0,0 +1,29 @@
+BSD 3-Clause License
+
+Copyright (c) 2025, Nosto
+All rights reserved.
+
+Redistribution and use in source and binary forms, with or without
+modification, are permitted provided that the following conditions are met:
+
+* Redistributions of source code must retain the above copyright notice, this
+  list of conditions and the following disclaimer.
+
+* Redistributions in binary form must reproduce the above copyright notice,
+  this list of conditions and the following disclaimer in the documentation
+  and/or other materials provided with the distribution.
+
+* Neither the name of the copyright holder nor the names of its
+  contributors may be used to endorse or promote products derived from
+  this software without specific prior written permission.
+
+THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS IS"
+AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
+IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
+DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT HOLDER OR CONTRIBUTORS BE LIABLE
+FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL
+DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR
+SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER
+CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY,
+OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE
+OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.

package/README.md

@@ -0,0 +1,154 @@
+# About Nosto
+
+If you are unfamiliar with Nosto as a company, you are welcome to visit out homepage at [https://nosto.com/](https://www.nosto.com/).
+
+If you wish to know more about our tech stack, we publish extensive documentation known as the [Techdocs](https://docs.nosto.com/techdocs).
+
+# Nosto CLI Tool
+
+A command-line interface to interact with Nosto's backend systems. Primarily aimed at developers and power-users who aim to use more powerful desktop tools for search-template development and (in the future) other features.
+
+<img width="862" alt="image" src="https://github.com/user-attachments/assets/d26869d2-cd03-4d04-a175-d544c45b99b1" />
+
+## Usage
+
+Nosto CLI aims to be as user-friendly as CLI tools get. You should be able to get up and running by utilizing the built-in `help` and `setup` commands, but a quick-start guide is also provided here.
+
+To start with, you may create an empty folder for your folder; or you may clone your git repository to work with.
+
+```bash
+# Install the CLI tool:
+npm i @nosto/nosto-cli -g
+
+# Login to Nosto
+# You will see the browser window open with further instructions.
+nosto login
+
+# Run the tool targeting a project directory:
+nosto status /path/to/project
+
+# Alternatively, `cd` into the project directory and omit the path
+cd /path/to/project && nosto status
+```
+
+## Configuration
+
+The recommended way to provide the configuration is a configuration file in the project folder, named `.nosto.json`. Alternatively, environmental variables can be used. If both are present, the environment takes precedence.
+
+See output of `nosto setup` for the full list of options.
+
+> You should never push the content of your `.nosto.json` to your git repository as it may contain sensitive data.
+
+### Required configuration
+
+At the minimum, one option is required: Merchant ID. If you're targeting an environment other than production, an API URL will also be required.
+
+> To quickly create a minimal configuration file, you may use the following command:
+> `NOSTO_MERCHANT=merchant-id nosto setup`
+
+#### Merchant ID:
+
+Public ID of the target merchant.
+
+> Property name in the config file: `merchant`<br/>
+> Property name in the env variable: `NOSTO_MERCHANT`
+
+#### API URL (Optional):
+
+By default, the CLI will try to contact production as the base URL. You may need to specify a different URL to target the correct environment.
+
+- Production URL: `https://api.nosto.com`
+- Staging URL: `https://api.staging.nosto.com`
+- Nosto internal development URL: `https://my.dev.nos.to/api`
+
+> Property name in the config file: `apiUrl` <br/>
+> Property name in the env variable: `NOSTO_API_URL`
+
+#### API Key (Optional):
+
+By default, the CLI will use your user credentials created by `nosto login`. If the API token is provided for a given project, it will be used instead.
+
+Your access key for the target merchant. Specifically, a private Nosto API_APPS token that you can find in the merchant admin settings.
+
+> Property name in the config file: `apiKey`<br/>
+> Property name in the env variable: `NOSTO_API_KEY`
+
+## Excluded files
+
+Nosto CLI takes the contents of your `.gitignore` file into account when pushing files to the remote, skipping all files matching these patterns. In addition, the CLI implicitly ignores any files or folders that start with `.`. I.e. `.nosto.json` is excluded automatically.
+
+During the pull, CLI downloads all files from the remote.
+
+> The `/build` folder is an exception to the rules above. It will never be skipped during pushing, even if added to .gitignore, and it is always ignored while pulling.
+
+### Recommended .gitignore
+
+```bash
+build
+.nosto.json
+.nostocache
+```
+
+## Supported commands
+
+You can use `nosto help` and variations to obtain detailed and up-to-date information on the current list of commands.
+
+- `login`
+  - Opens the browser window to start the login flow.
+  - Stores the credentials (email and temporary access token) in `~/.nosto/.auth.json`
+- `logout`
+  - Wipes the stored login credentials
+- `setup [projectPath]`
+  - Prints setup information and creates a placeholder config file if needed
+- `status [projectPath]`
+  - Reads the configuration and prints the general status
+- `st [projectPath]`
+  - Alias: `search-templates [projectPath]`
+  - Search templates related commands
+  - `st pull [projectPath]`
+    - Fetches the current remote state for the configured merchant
+  - `st push [projectPath]`
+    - Pushes the local state to the remote for the configured merchant
+  - `st build [projectPath]`
+    - For a modern search-template project, it invokes the `onBuild` script in `nosto.config.ts`
+    - For a legacy search-template project, it mirrors the hosted VSCode Web build workflow
+  - `st dev [projectPath]`
+    - Watches files, build and upload automatically
+    - For a modern search-template project, it invokes the `onBuildWatch` script in `nosto.config.ts`
+    - For a legacy search-template project, it uses esbuild to watch files, build and upload automatically. Only uploads build artifacts, not the sources.
+
+## External dependencies in legacy search-templates
+
+With the addition of local builds, the external dependencies are something that is theoretically possible. However, due to complexities of the legacy setup, external deps **will not be officially supported in the legacy templates**. We understand that this is something modern web development needs, and we are addressing that by our upcoming open source search-templates offering. Specifically, search-templates-starter, [search-js](https://github.com/nosto/search-js) and this very CLI tool.
+
+If you would still like to try your luck with introducing dependencies into a legacy app, we recommend you stick with only build-time dependencies like TypeScript that disappear at runtime. In that case, build your app as you would, and point the CLI's build to the output folder.
+
+## Development
+
+### Testing
+
+This project uses [Vitest](https://vitest.dev/) as the test runner. Tests are organized under the `test/` directory mirroring the structure of `src/`.
+
+#### Available scripts
+
+```bash
+# Run tests once
+npm run test
+
+# Run tests in watch mode
+npm run test:watch
+
+# Run tests with UI
+npm run test:ui
+
+# Run tests with coverage report
+npm run test:coverage
+```
+
+## Known issues
+
+### Search templates push reports no files changed
+
+Running `nosto st push` after `nosto st dev` without changing any files will stop early with the "No files to push" message due to the hashing mechanism not taking the pushed paths into account properly.
+
+**Workaround**: Use `nosto st push -f` or change any of the files to update the hash.

package/commitlint.config.js

@@ -0,0 +1,4 @@
+export default {
+  extends: ["@commitlint/config-conventional"],
+  ignores: [message => /\[skip ci\]/.test(message)]
+}