41 releases 41 tags

RSS feed

• v0.13.10 82241de0dd

  Compare

  git-next-v0.13.10 Pre-release

  kemitix released this 2024-09-12 21:02:02 +01:00 | 27 commits to dev since this release

  Added

  • (config) Optionally specify max commits between dev and main

  By default git-next will only support the dev branch being at most 25 commits ahead of main. This should be enough to most users. However, if you want, or need, to add more than 25 commits to your dev branch, for example when you are working offline for an extended period of time, you can now add different limit to your git-next-server.toml file for the required forge. e.g.:

  [forge.github]
  forge_type = "GitHub"
  hostname = "github.com"
  user = "username"
  token = "api-key"
  max_dev_commits = 50
  

  Fixed

  • (tui) make tui work from docker image

  You can now use the TUI interface from the Docker image:

  docker run -it -p "8888:8888" -v .:/app/ git.kemitix.net/kemitix/git-next:latest server start --ui
  

  Remember to specify the storage.path in your git-next-server.toml to be within the /app directory, and to map the port your webhook notifications are being delivered to to the port defined in `listen.http.port'. e.g.:

  [listen]
  http = { addr = "0.0.0.0", port = 8888 }
  
  [storage]
  path = "/app/data"
  

  • (tui) alerts, such as WIP aren't being reset

  When an alert was raised for a repo, it wasn't being reset when it was cleared for some repos.

  • (test) tests requiring .git pass when not present

  Development only: I've started using Jujutsu for my local development, and when you use jj to clone the repo it doesn't create a .git directory. Some of the tests for git-next require that directory and would fail otherwise. Now they silently pass. They will still be run properly when they are in CI, so the tests are still valid.

  • (tui) update ui when push next or main finishes

  Removed the 10 second pause after completing any git push for next or main branches before updating the status message for a repo.

  • (tui) don't set background for normal repo alias

  The repo alias label's background had been explicitly set to black, which on a dark terminal was okay, but look bad on a light terminal. Now the background is whatever the default is.

  Downloads

  • Source code (ZIP)
    1 download
  • Source code (TAR.GZ)
    2 downloads