Movatterモバイル変換

[0]ホーム
URL:

Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

 Sign up
Appearance settings
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 orlearn 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:libgit2/libgit2
Failed to load repositories. Confirm that selected base ref is valid, then try again.
Loading
base:main
Choose a base ref
Loading
...
head repository:libgit2/libgit2
Failed to load repositories. Confirm that selected head ref is valid, then try again.
Loading
compare:ethomson/notification
Choose a head ref
Loading
  • 5commits
  • 11files changed
  • 1contributor

Commits on Mar 3, 2025

  1. notifications: a notification system for callers

    Users can now configure a "notification callback"; notifications areraised when a condition occurs in a git repository that an end-usershould know about, or that the calling application may wish to act on.Notifications provide structured data, that is provided based on thetype of notification (for example, file paths).In addition, an an informative message is provided when a notificationis raised; the structured data should be sufficient for callers to buildtheir own message, but the provided message should make thatunnecessary.Some examples of likely future use of notifications:* `core.safecrlf=warn` messages are warning-level notifications. This  allows the calling application to receive these notifications and  display them to the user (for example, sending them to the console).* When a file cannot be written during checkout, we should inform the  calling application. By default, git continues to check out when one  (or more) paths fail to be written, but conclude that the checkout  failed overall. Given this somewhat odd behavior, callers may wish to  short-circuit this when any path fails to be written.* Callers may want structured failure information for a `safe.directory`  failure so that they can get the file path without having to try to  "screen scrape" the git_error message.
    @ethomson
    ethomson committedMar 3, 2025
    Configuration menu
    Copy the full SHA
    8cc0fc4View commit details
    Browse the repository at this point in the history

  2. filter: produce warnings whencore.safecrlf=warn

    Produce warning-level notifications when `core.safecrlf=warn`.
    @ethomson
    ethomson committedMar 3, 2025
    Configuration menu
    Copy the full SHA
    5ba12e3View commit details
    Browse the repository at this point in the history

  3. filter: assert on invalid crlf state

    Produce an assertion when internally invalid CRLF configuration stateexists.
    @ethomson
    ethomson committedMar 3, 2025
    Configuration menu
    Copy the full SHA
    808e6e8View commit details
    Browse the repository at this point in the history

  4. cli: add a notification handler

    Provide a notification handler in the CLI so that (for example) warningsand non-fatal error information can be sent to stdout. The CLI ignores"fatal" level errors since they're superfluous; it will get the sameerror after the function returns.
    @ethomson
    ethomson committedMar 3, 2025
    Configuration menu
    Copy the full SHA
    d7b1167View commit details
    Browse the repository at this point in the history

  5. checkpoint

    @ethomson
    ethomson committedMar 3, 2025
    Configuration menu
    Copy the full SHA
    ddaaab7View commit details
    Browse the repository at this point in the history
Loading
[8]ページ先頭
©2009-2025 Movatter.jp