Skip to content
Permalink

Comparing changes

Choose two branches to see what’s changed or to start a new pull request. If you need to, you can also or learn more about diff comparisons.

Open a pull request

Create a new pull request by comparing changes across two branches. If you need to, you can also . Learn more about diff comparisons here.
base repository: Mubashwer/git-mob
Failed to load repositories. Confirm that selected base ref is valid, then try again.
Loading
base: v1.7.0
Choose a base ref
...
head repository: Mubashwer/git-mob
Failed to load repositories. Confirm that selected head ref is valid, then try again.
Loading
compare: v1.8.0
Choose a head ref
  • 3 commits
  • 10 files changed
  • 2 contributors

Commits on Jun 9, 2025

  1. ci: fix building for aarch64 linux target using cross

    Download aarch64-linux-musl-gcc linker step in upload-binaries job was failing for aarch64 linux target
    
    See https://github.com/Mubashwer/git-mob/actions/runs/15495275177/job/43673822229
    Mubashwer committed Jun 9, 2025
    Configuration menu
    Copy the full SHA
    2ea0d3d View commit details
    Browse the repository at this point in the history

Commits on Jun 10, 2025

  1. feat: make --global the default behavior for setup command (#100)

    * feat: make --global the default behavior for setup command
    
    Previously, the setup command required explicit --global or --local flags
    and would show help when no arguments were provided. This change makes
    --global the default behavior, simplifying the common use case while
    maintaining backward compatibility.
    
    Changes:
    - Remove arg_required_else_help constraint from Setup command
    - Make setup command default to global behavior when no flags specified
    - Hide --global flag from help output while keeping it functional for
      backward compatibility
    - Update command description to clarify global setup is default
    - Update all documentation examples from "git mob setup --global" to
      "git mob setup"
    
    The --global flag is still accepted but hidden from help output to avoid
    confusion while ensuring existing scripts and workflows continue to work.
    The --local flag remains unchanged and is only needed for repositories
    that override core.hooksPath (e.g., when using husky).
    
    This aligns with user expectations since global setup was the standard
    installation method, with local setup being a specialized use case for
    repositories with custom hook configurations.
    
    * fix: correct grammar in setup command description
    Mubashwer authored Jun 10, 2025
    Configuration menu
    Copy the full SHA
    72a41b9 View commit details
    Browse the repository at this point in the history
  2. Configuration menu
    Copy the full SHA
    c78e4da View commit details
    Browse the repository at this point in the history
Loading