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: ruby-git/ruby-git
Failed to load repositories. Confirm that selected base ref is valid, then try again.
Loading
base: d6ec05e
Choose a base ref
...
head repository: ruby-git/ruby-git
Failed to load repositories. Confirm that selected head ref is valid, then try again.
Loading
compare: 3137426
Choose a head ref
  • 6 commits
  • 7 files changed
  • 2 contributors

Commits on Feb 27, 2025

  1. chore: release v3.0.0

    Signed-off-by: James Couball <jcouball@yahoo.com>
    jcouball committed Feb 27, 2025
    Configuration menu
    Copy the full SHA
    1a5092a View commit details
    Browse the repository at this point in the history

Commits on Feb 28, 2025

  1. Configuration menu
    Copy the full SHA
    b060e47 View commit details
    Browse the repository at this point in the history
  2. Configuration menu
    Copy the full SHA
    f407b92 View commit details
    Browse the repository at this point in the history
  3. Configuration menu
    Copy the full SHA
    9d44146 View commit details
    Browse the repository at this point in the history

Commits on May 14, 2025

  1. Improved error message of rev_parse

    As described by git-rev-parse:
      Many Git porcelainish commands take mixture of flags (i.e. parameters
      that begin with a dash -) and parameters meant for the underlying git
      rev-list command they use internally and flags and parameters for the
      other commands they use downstream of git rev-list. This command is
      used to distinguish between them.
    
    Using the `--` to separate revisions from paths is at the core of git.
    I do not think this behavior will ever change.
    
    The message without the extra parameters:
      fatal: ambiguous argument 'v3': unknown revision or path not in the
      working tree.
      Use '--' to separate paths from revisions, like this:
      'git <command> [<revision>...] -- [<file>...]'
    
    The message with new parameters:
      fatal: bad revision 'NOTFOUND'
    
    I think it's way more descriptive.
    mpapis authored and jcouball committed May 14, 2025
    Configuration menu
    Copy the full SHA
    b47eedc View commit details
    Browse the repository at this point in the history
  2. chore: release v3.0.1

    Signed-off-by: James Couball <jcouball@yahoo.com>
    jcouball committed May 14, 2025
    Configuration menu
    Copy the full SHA
    3137426 View commit details
    Browse the repository at this point in the history
Loading