Skip to content

Missing callback on ahead behind changing. #10

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.

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

Open
chris-addison opened this issue Sep 17, 2019 · 0 comments
Open

Missing callback on ahead behind changing. #10

chris-addison opened this issue Sep 17, 2019 · 0 comments
Labels
bug Something isn't working

Comments

@chris-addison
Copy link
Contributor

chris-addison commented Sep 17, 2019

Prerequisites

  • Be sure to run with tracing enabled to capture runtime details in the log file
  • Include the log file in the PR.
    • On Windows, the extension log file is at %LOCALAPPDATA%\GitHubUnity\github-unity.log
    • On macOS, the extension log file is at ~/Library/Logs/GitHubUnity/github-unity.log
    • On linux, the extension log file is at ~/.local/share/GitHubUnity/github-unity.log

Description

Ahead and behind updating via git fetch are not sending the Environment.Repository.TrackingStatusChanged event.

Steps to Reproduce

  1. register a simple logging handler to Environment.Repository.TrackingStatusChanged
  2. Push a new commit to remote from another local checkout
  3. Call git fetch from G4U
  4. Observe no callback.

Expected behavior: Callback should occur.
Actual behavior: Nothing.

Reproduces how often: 100% of the time.

Additional Information

Any additional information, configuration or data that might be necessary to reproduce the issue.

@chris-addison chris-addison added the bug Something isn't working label Sep 17, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

1 participant