gregsexton/gitv

Version 1.4 - Testing

Open

#131 opened on Jun 10, 2018

View on GitHub
 (0 comments) (0 reactions) (0 assignees)Vim script (879 stars) (53 forks)batch import
help wanted

Description

We need help testing the 1.4 release! If you use OSX or Windows, or have a custom setup, please help us out.

Please post below or contact me if you test something out and I can mark it off the list. Please contact me by email or matrix or post here if you want to be added as a contributor.

  • General issues
    • Proof reading documentation
    • General testing on Windows
    • General testing on OSX
  • Updated features from v1.3
    • :Gitv autocompletion (including with globs)
    • gitv#util#line#refs()/gitv#util#line#sha()
    • Calling arbitrary commands with :Git from inside the branch viewer
    • All commands with/without counts
    • Confirming fast forward on merge
    • Passing in --all from :Gitv and still toggling all with a
  • New features from v1.3
    • Adding extra args to the gitv command
    • Cherry pick (visual/normal)
    • Reset branch (soft/hard) (visual/normal)
    • Reversion (visual/normal)
    • Bisecting (start/stop/next/good/bad and other commands - see docs) (visual and normal commands)
    • Rebasing (using every method to start and doing every action - see docs) (visual and normal commands)
    • Custom keymappings (all keys with/without)
    • :Gitv (filename) and :Gitv (dirname)
    • Passing options with g:gitvPreviewWindow
    • Test whether windows works with g:Gitv_DisableShellEscape (post result)
    • GitvSetupBuffer autocmd
    • Toggling between the preview and branch window with gw
    • Wide string support
    • Long git hash support
    • Gitv_GetDebugInfo()
  • Bugfixes from v1.3
    • Hardcoded nosplitright and nosplitbelow, should not break layout
  • New options from v1.3
    • g:Gitv_DoNotMapCtrlKey
    • g:Gitv_QuietBisect
    • g:Gitv_MergeArgs

Contributor guide

Tech stack
None
Domain
testing
Issue type
test
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
1
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
half day
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
stale
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
mostly clear
Prerequisites
Vim basicsgit version control
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
80
Research direction
The issue lists many testing tasks for the gitv plugin v1.4 release. A contributor should start by reading the checklist, picking a task like 'Proof reading documentation' or 'General testing on Windows', and reporting results. No prior comments or linked PRs exist, so the work is independent. The repository uses Vim script, but no specific files are mentioned; exploration of the codebase may be needed for feature specific tests.