Skip to content

Actions: JeffFaer/tmux-vcs-sync

Actions

All workflows

Actions

Loading...
Loading

Showing runs from all workflows
320 workflow runs
320 workflow runs

Filter by Event

Filter by Status

Filter by Branch

Filter by Actor

feat(cli): Optionally generate shell completion files.
git #24: Pull request #9 opened by JeffFaer
February 18, 2024 21:57 42s completion
February 18, 2024 21:57 42s
A bunch of commits all bundled into one PR
git #23: Pull request #8 opened by JeffFaer
February 18, 2024 20:55 35s git_rebase_fix
February 18, 2024 20:55 35s
A bunch of commits all bundled into one PR
tmux-vcs-sync #23: Pull request #8 opened by JeffFaer
February 18, 2024 20:55 2m 25s git_rebase_fix
February 18, 2024 20:55 2m 25s
A bunch of commits all bundled into one PR
api #23: Pull request #8 opened by JeffFaer
February 18, 2024 20:55 28s git_rebase_fix
February 18, 2024 20:55 28s
test(git): Remove a debug line I left in the last PR.
tmux-vcs-sync #22: Pull request #7 synchronize by JeffFaer
February 17, 2024 16:01 37s debug_op
February 17, 2024 16:01 37s
test(git): Remove a debug line I left in the last PR.
git #22: Pull request #7 synchronize by JeffFaer
February 17, 2024 16:01 2m 24s debug_op
February 17, 2024 16:01 2m 24s
test(git): Remove a debug line I left in the last PR.
api #22: Pull request #7 synchronize by JeffFaer
February 17, 2024 16:01 23s debug_op
February 17, 2024 16:01 23s
test(git): Make sure we're running git without a local config when testing.
tmux-vcs-sync #21: Pull request #6 opened by JeffFaer
February 17, 2024 15:32 2m 25s git_config
February 17, 2024 15:32 2m 25s
test(git): Add basic tests for how git should work at the api.Repository level.
git #20: Pull request #5 synchronize by JeffFaer
February 17, 2024 00:59 25s git_test
February 17, 2024 00:59 25s
test(git): Add basic tests for how git should work at the api.Repository level.
tmux-vcs-sync #20: Pull request #5 synchronize by JeffFaer
February 17, 2024 00:59 23s git_test
February 17, 2024 00:59 23s
test(git): Add basic tests for how git should work at the api.Repository level.
api #20: Pull request #5 synchronize by JeffFaer
February 17, 2024 00:59 20s git_test
February 17, 2024 00:59 20s
test(git): Add basic tests for how git should work at the api.Repository level.
api #19: Pull request #5 synchronize by JeffFaer
February 17, 2024 00:47 14s git_test
February 17, 2024 00:47 14s
test(git): Add basic tests for how git should work at the api.Repository level.
tmux-vcs-sync #19: Pull request #5 synchronize by JeffFaer
February 17, 2024 00:47 25s git_test
February 17, 2024 00:47 25s
test(git): Add basic tests for how git should work at the api.Repository level.
git #19: Pull request #5 synchronize by JeffFaer
February 17, 2024 00:47 27s git_test
February 17, 2024 00:47 27s
test(git): Add basic tests for how git should work at the api.Repository level.
api #18: Pull request #5 opened by JeffFaer
February 17, 2024 00:40 2m 26s git_test
February 17, 2024 00:40 2m 26s
test(git): Add basic tests for how git should work at the api.Repository level.
tmux-vcs-sync #18: Pull request #5 opened by JeffFaer
February 17, 2024 00:40 40s git_test
February 17, 2024 00:40 40s
fix(git): Don't require that git repos have an origin when determining
api #16: Pull request #3 opened by JeffFaer
February 13, 2024 16:48 2m 25s no_origin
February 13, 2024 16:48 2m 25s
fix(git): Don't require that git repos have an origin when determining
tmux-vcs-sync #16: Pull request #3 opened by JeffFaer
February 13, 2024 16:48 39s no_origin
February 13, 2024 16:48 39s
fix(git): Don't require that git repos have an origin when determining
git #16: Pull request #3 opened by JeffFaer
February 13, 2024 16:48 38s no_origin
February 13, 2024 16:48 38s
ProTip! You can narrow down the results and go further in time using created:<2024-02-13 or the other filters available.