wip

Author: edulix

.claude/README.md

@@ -56,7 +56,7 @@ export GITHUB_TOKEN="ghp_..."    # Set GitHub token
 
 ### 2. Sync GitHub Data
 ```bash
-release-tool sync                 # Sync issues, PRs, releases
+release-tool pull                 # Sync issues, PRs, releases
 ```
 
 ### 3. Generate Release Notes
@@ -138,7 +138,7 @@ See `.claude/commands/` for custom slash commands:
 ## Important Files
 
 - `release_tool.toml` - Configuration file (created by `init-config`)
-- `release_tool.db` - SQLite cache (auto-created by `sync`)
+- `release_tool.db` - SQLite cache (auto-created by `pull`)
 - `.release_tool_cache/` - Cloned git repositories for offline access
 - `docs/` - User documentation
 - `tests/` - Comprehensive unit tests

.release_tool.toml

@@ -54,9 +54,9 @@ api_url = "https://api.github.com"
 path = "release_tool.db"
 
 # =============================================================================
-# Sync Configuration
+# Pull Configuration
 # =============================================================================
-[sync]
+[pull]
 # cutoff_date: Only fetch issues/PRs created after this date (ISO format: YYYY-MM-DD)
 # This limits historical data fetching and speeds up initial sync
 # Example: "2024-01-01" to only fetch data from 2024 onwards
@@ -80,8 +80,8 @@ clone_code_repo = true
 # Default: null (uses .release_tool_cache/{repo_name})
 # code_repo_path = "/path/to/local/repo"
 
-# show_progress: Show progress updates during sync
-# When true, displays messages like "syncing 13 / 156 issues (10% done)"
+# show_progress: Show progress updates during pull
+# When true, displays messages like "pulling 13 / 156 issues (10% done)"
 # Default: true
 show_progress = true
 
@@ -158,7 +158,7 @@ unclosed_issue_action = "warn"
 #
 # "Partial matches" occur when:
 #   - Issue key extracted from branch/PR, but issue not in database (common causes):
-#     * Issue created before your sync cutoff date
+#     * Issue created before your pull cutoff date
 #     * Issue doesn't exist (typo in branch name)
 #     * Sync hasn't been run yet
 #   - Issue found in database, but in wrong repository:

README.md

@@ -84,7 +84,7 @@ jobs:
         env:
           GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
         run: |
-          release-tool sync
+          release-tool pull
           release-tool generate ${{ github.event.inputs.version }} --upload
 ```
 
@@ -93,7 +93,7 @@ jobs:
 If you need to use SSH (e.g., for private repos without token access), configure your `release_tool.toml`:
 
 ```toml
-[sync]
+[pull]
 clone_method = "ssh"  # Options: "https", "ssh", "auto" (default)
 ```
 
@@ -109,7 +109,7 @@ Then set up SSH keys in your workflow:
   env:
     GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}  # Still needed for API calls
   run: |
-    release-tool sync
+    release-tool pull
     release-tool generate ${{ github.event.inputs.version }}
 ```
 
@@ -129,7 +129,7 @@ For GitHub Enterprise or custom Git servers:
 [github]
 api_url = "https://github.enterprise.com/api/v3"
 
-[sync]
+[pull]
 clone_url_template = "https://github.enterprise.com/{repo_full_name}.git"
 ```
 
@@ -167,9 +167,9 @@ If you encounter clone errors:
    export GITHUB_TOKEN="your_github_token"
    ```
 
-4. **Sync repository data**:
+4. **Pull repository data**:
    ```bash
-   release-tool sync
+   release-tool pull
    ```
 
 5. **Generate release notes**:
@@ -179,10 +179,10 @@ If you encounter clone errors:
 
 ## CLI Commands
 
-### `sync`
-Sync repository data from GitHub to the local database:
+### `pull`
+Pull repository data from GitHub to the local database:
 ```bash
-release-tool sync [repository] [--repo-path PATH]
+release-tool pull [repository] [--repo-path PATH]
 ```
 
 ### `generate`
@@ -226,9 +226,9 @@ issue_repo = "owner/issues"  # Optional: separate repo for issues
 default_branch = "main"
 ```
 
-### Sync Configuration
+### Pull Configuration
 ```toml
-[sync]
+[pull]
 clone_code_repo = true  # Whether to clone the repository locally
 clone_method = "auto"   # Options: "https", "ssh", "auto" (default)
 clone_url_template = ""  # Custom clone URL template (optional)
@@ -364,7 +364,7 @@ export GITHUB_TOKEN="ghp_your_token"
 # 2. Edit release_tool.toml with your repo settings
 
 # 3. Sync GitHub data once or periodically
-release-tool sync
+release-tool pull
 
 # 4. Generate release notes for version 2.0.0
 release-tool generate 2.0.0 \

docs/doc/branching-strategy.md

@@ -154,9 +154,9 @@ $ release-tool generate 9.0.5 --repo-path .
    # Run tests, build, etc.
    ```
 
-4. **Publish Release**
+4. **Push Release**
    ```bash
-   release-tool publish 9.1.0 -f notes.md
+   release-tool push 9.1.0 -f notes.md
    ```
 
 ## Custom Branch Templates

docs/doc/configuration.md

@@ -73,7 +73,7 @@ Sensitive information like tokens should be set via environment variables:
 - `token`: (Optional) GitHub Personal Access Token. Recommended to use `GITHUB_TOKEN` environment variable instead.
 - `api_url`: (Optional) GitHub API URL. Default is `https://api.github.com`. Use for GitHub Enterprise.
 
-### `sync`
+### `pull`
 
 Configuration for syncing data from GitHub.
 
@@ -96,7 +96,7 @@ Configuration for syncing data from GitHub.
 - **Default**: `"auto"`
 - **Example**:
   ```toml
-  [sync]
+  [pull]
   clone_method = "https"  # For GitHub Actions
   ```
 
@@ -105,7 +105,7 @@ Configuration for syncing data from GitHub.
 - **Description**: Custom clone URL template for GitHub Enterprise or custom Git servers. Use `{repo_full_name}` as placeholder.
 - **Example**:
   ```toml
-  [sync]
+  [pull]
   clone_url_template = "https://github.enterprise.com/{repo_full_name}.git"
   ```
 

docs/doc/development.md

@@ -50,7 +50,7 @@ Standard unit tests covering:
 - Policies and business logic (`test_policies.py`)
 - Template rendering (`test_output_template.py`, `test_default_template.py`)
 - Issue management (`test_query_issues.py`, `test_partial_issues.py`)
-- Publishing and syncing (`test_publish.py`, `test_sync.py`)
+- Pushing and syncing (`test_push.py`, `test_pull.py`)
 
 ```bash
 # Run all unit tests except Docker tests

docs/doc/intro.md

@@ -18,9 +18,9 @@ The **Release Tool** is a CLI application designed to manage releases using sema
 - **Semantic Versioning**: Automatically determines the next version based on changes.
 - **Release Notes Generation**: Groups and formats release notes from Pull Requests and issues.
 - **Policy-Driven**: Highly configurable policies for versioning, issue extraction, and grouping.
-- **GitHub Integration**: Syncs data from GitHub and creates releases.
-- **GitHub Actions Bot**: Automate releases with ChatOps and auto-publishing ([Release Bot](release-bot.md)).
-- **Multiple Release Modes**: Draft, published, and just-publish modes for different workflows.
+- **GitHub Integration**: Pulls data from GitHub and creates releases.
+- **GitHub Actions Bot**: Automate releases with ChatOps and auto-pushing ([Release Bot](release-bot.md)).
+- **Multiple Release Modes**: Draft, published, and just-push modes for different workflows.
 - **SQLite Storage**: Caches repository data locally for efficiency.
 
 ## Goals

docs/doc/issues.md

@@ -24,7 +24,7 @@ The `issues` command allows you to search and inspect issues that have been sync
 - **Offline access** - Query issues without internet connectivity
 
 :::caution Prerequisites
-This command only searches issues that have been synced. Make sure to run `release-tool sync` first to populate your local database.
+This command only searches issues that have been synced. Make sure to run `release-tool pull` first to populate your local database.
 :::
 
 ## Smart ISSUE_KEY Format
@@ -256,7 +256,7 @@ If you see:
 
 Issues not found in database (1):
   • 8853 (from branch feat/meta-8853/main, PR #2122)
-    → Issue may be older than sync cutoff date
+    → Issue may be older than pull cutoff date
     → Issue may not exist (typo in branch/PR)
     → Sync may not have been run yet
 ```
@@ -280,7 +280,7 @@ Issues not found in database (1):
 
 4. If not found, verify on GitHub or re-run sync:
    ```bash
-   release-tool sync
+   release-tool pull
    ```
 
 ### Scenario 2: Issue in Different Repo
@@ -418,7 +418,7 @@ Since results are sorted by `created_at DESC`, the first results show the newest
 release-tool issues --limit 10
 ```
 
-### 5. Verify Sync Coverage
+### 5. Verify Pull Coverage
 
 Check if issues from a specific time period are synced:
 
@@ -435,36 +435,36 @@ release-tool issues --limit 1000 --format csv > all_issues.csv
 
 **Error:**
 ```
-Error: Database not found. Please run 'release-tool sync' first.
+Error: Database not found. Please run 'release-tool pull' first.
 ```
 
 **Solution:**
 ```bash
-release-tool sync
+release-tool pull
 ```
 
-The database is created by the `sync` command. If you've never synced, the database doesn't exist yet.
+The database is created by the `pull` command. If you've never synced, the database doesn't exist yet.
 
 ### "Repository 'X' not found in database"
 
 **Error:**
 ```
 Error: Repository 'sequentech/unknown' not found in database.
-Tip: Run 'release-tool sync' to fetch repository data.
+Tip: Run 'release-tool pull' to fetch repository data.
 ```
 
 **Solutions:**
 1. Check the repository name spelling
 2. Ensure the repository is configured in `release_tool.toml`
-3. Run `release-tool sync` to fetch repository metadata
+3. Run `release-tool pull` to fetch repository metadata
 
 ### No Results Found
 
 If your query returns no results:
 
 1. Verify issues exist on GitHub
-2. Check your sync cutoff date (might be excluding old issues)
-3. Re-run sync: `release-tool sync`
+2. Check your pull cutoff date (might be excluding old issues)
+3. Re-run sync: `release-tool pull`
 4. Try fuzzy matching instead of exact match
 
 ### CSV Output Looks Wrong in Terminal