Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Suggest full-path refresh() in failure message #1844

Merged
merged 2 commits into from
Feb 24, 2024
Merged

Suggest full-path refresh() in failure message #1844

merged 2 commits into from
Feb 24, 2024

Commits on Feb 23, 2024

  1. Fix ambiguous wording in Git.refresh docstring

    @EliahKagan
    EliahKagan committed Feb 23, 2024
    Configuration menu
    Copy the full SHA
    7d96a1a View commit details
    Browse the repository at this point in the history

  2. Suggest full-path refresh() in failure message 

    This does not suggest or recommend *preferring* to explicitly call
refresh() over the other other techniques, but it clarifies that
the use of refresh() being presented needs a path argument. It also
shows that path in the form of a full path, so users are less
likely to be misled into thinking a command name or other relative
path should be passed to refresh(), which should rarely be done
(since refresh(path) resolves path).
    @EliahKagan
    EliahKagan committed Feb 23, 2024
    Configuration menu
    Copy the full SHA
    b8ebff8 View commit details
    Browse the repository at this point in the history