All Versions
21
Latest Version
Avg Release Cycle
169 days
Latest Release
1535 days ago

Changelog History
Page 1

  • v3.2.2 Changes

    November 07, 2020
    • 🛠 Fix (#27: Concurrency issue starting many githudd
      daemon that would never be cleaned up

  • v3.2.1 Changes

    February 09, 2020

    GHC 8.8 compatibility

  • v3.2.0 Changes

    January 31, 2020
    • 🛠 Fix (#21): use the system defined temp location
      0️⃣ as default for the PID and socket location rather than an hardcoded path that does not exist on
      all systems
    • 0️⃣ Feat: Do not display background server error/restart on STDERR by default. Only display it if the
      env variable GITHUD_DEBUG is set to TRUE

  • v3.1.0 Changes

    August 16, 2019

    👀 I seem to have rushed to deliver the background fetcher. While it worked well "interactively", it seems it was not very robust to external events/failures (would stay stuck on absence of internet, on mac getting out of hibernation, ...)

    🚀 I promptly released 3.0.1 that de-activated the background fetcher by default.

    🛠 Now I think I have fixed the issues. The background fetcher has been running on my machine for a week without issues, or rather recovering properly following issues.

    I'm releasing it again. 3.1.0 is just the re-enabling of what should have been working in 3.0.0

    Have fun

  • v3.0.2 Changes

    • 🛠 Fix: githudd to restart from scratch if there is an issue with the pid file / background process
    • 🛠 Fix: githudd to ignore failing git fetch return code
    • 🛠 Fix: githudd recover on client/server exception

  • v3.0.1 Changes

    August 09, 2019
    • 🛠 Fix: Disable githudd by default. Seems that due to the socket communication I have made it unstable resulting in githud not displaying anything. Let's say that githudd is Beta. I'll work on making it recover on failure

  • v3.0.0 Changes

    August 04, 2019

    Backgroud Fetcher, the missing feature

    It was missing, you wanted it, it's now there.
    Githud has been enriching your prompt and your GIT context awareness for years. One thing was missing though: it failed to tell you what was happening on the remote while you were working.

    ✅ Well this is from the past. From now on, githud will launch a daemon (githudd) that will regularly fetch the latest state of your remote(s) (defaults to every 30s).

    From the changelog:

    • Feat: Add a daemon called githudd that will continuously fetch the last git folder where
      githud was executed. In a typical install where githud is used in the prompt, that means the
      last git folder browsed.

    • 🔧 Config: some new configuration has been added for the githudd daemon. The default values have
      ✅ been tested on Mac. You can find this new section in the .githudrc file in this repo. The new
      0️⃣ parameters are also pasted below along with their default values.

      -------------------------------------------------------------------------------------------

      The following config controls the background fetcher daemon behavior called githudd

      -------------------------------------------------------------------------------------------

      run_fetcher_daemon=True

      githudd_sleep_seconds=30 # how long does the daemon sleep between cycles

      githudd_pid_file_path=/usr/local/var/run/githudd.pid

      githudd_socket_file_path=/usr/local/var/run/githudd.socket

      # Githudd logs can be verbose. They are here for debugging only. It is not advised that you

      # activate them

      githudd_log_file_path=/dev/null

  • v2.1.0 Changes

    August 12, 2018
    • 👍 Feat: Add support for TMUX with githud tmux. You can now use tmux inside the status bar or the pane title of TMUX for example
    • 👍 Feat: Add support for no output formatting with githud none.

  • v2.0.2 Changes

    April 04, 2018
    • 🛠 Fix: Properly reset "normal" styling after displaying "Bold" characters (#13)

  • v2.0.1 Changes

    • 💥 BREAKING: the executable is renamed from gitHUD to githud, as suggested in #14 by @voidus