Giter Site home page Giter Site logo

joseluisq / gitnow Goto Github PK

View Code? Open in Web Editor NEW
379.0 6.0 24.0 221 KB

Speed up your Git workflow. :tropical_fish:

Home Page: https://github.com/joseluisq/gitnow

License: MIT License

Shell 100.00%
git git-workflow fish-shell fish-packages ssh bitbucket keybindings github semver

gitnow's Introduction

GitNow CI Releases

Speed up your Git workflow. ๐Ÿ 

GitNow contains a command set that provides high-level operations on the top of Git.
A Fish shell alternative inspired by git-friendly.

Install

Stable:

Paket

paket add joseluisq/[email protected]

Fisher

fisher install joseluisq/[email protected]

Fundle

fundle plugin joseluisq/gitnow --url '[email protected]:joseluisq/gitnow.git#tags/2.12.0'

Latest changes:

paket add joseluisq/gitnow

# Or
fisher install joseluisq/gitnow

# Or
fundle plugin joseluisq/gitnow

Note: Use that method if you don't want to wait for a new release.

Commands

Command Shortcut Description
gitnow Show available commands and version info.
Git
state Alt + S Show the working tree status in a compact way.
stage Alt + E Stage files in current working directory.
unstage Ctrl + E Unstage files in current working directory.
show Alt + M Show commit detail objects.
untracked Check for untracked files and directories.
commit Commit changes to the repository.
commit-all Alt + C Add and commit all changes to the repository.
tag List and create release tag versions following Semver 2.0.
pull Alt + D Pull changes from remote server but saving uncommitted changes.
push Alt + P Push commit changes to remote repository.
upstream Alt + U Commit all changes and push them to remote server.
move Moves from current branch to another but stashing your changes.
merge Merges a local branch into the active one.
assume Ignores changes in certain files temporarily.
logs Alt + L Shows logs in a fancy way.
Gitflow
feature (1) Alt + F Creates a new feature (Gitflow) branch from current branch.
hotfix (1) Alt + H Creates a new hotfix (Gitflow) branch from current branch.
bugfix (1) Creates a new bugfix (Gitflow) branch from current branch.
release (1) Creates a new release (Gitflow) branch from current branch.
Bonus
github Clone a GitHub repository using SSH.
bitbucket Clone a Bitbucket Cloud repository using SSH.

Note:

  • (1) This command key binding can creates a new branch taking as name some text of the clipboard (optional).

Tips

  • Skip the password request creating a SSH key for your Github or Bitbucket account.
  • SSH setup is required for using github and bitbucket commands.
  • Take advantage of keybindings in order to get faster operations.

Gitnow configuration file

To configure Gitnow just copy the .gitnow default file and place it in your home directory (~/.gitnow).

Options

The [ options ] section contains some options in order to adjust centain Gitnow behaviour.

For more details about the options please take a look at .gitnow file content.

Keybindings

The .gitnow file contains a [ keybindings ] section with default shortcuts (key-value pairs). But you can add, edit or remove keybindings on demand. If you want custom keybindings for your commands just run fish_key_reader in your terminal, then press the key or key's combinations to get the right characters sequence and finally set it to your preferred command in your ~/.gitnow file.

Usage

gitnow

Show available commands and version info.

gitnow

state

Show the working tree status in compact way.

state
Current working tree status:
## master...origin/master
 M README.md
 M conf.d/gitnow.fish

stage

Stage files in current working directory.

Note: This command does git add . by default. Add your git add flags as usual to overwrite it.

# a) git add . (by default)
stage
# b) custom 1
stage README.md LICENSE.md
# c) custom 2
stage . --ignore-errors

unstage

Unstage files in current working directory.

Note: This command does git reset . by default. Add your git reset flags as usual to overwrite it.

# a) git reset . (by default)
unstage
# b) custom 1
unstage README.md LICENSE.md
# c) custom 2
unstage --soft HEAD

show

Show commit detail objects.

Note: This command does git show --compact-summary HEAD by default. Add your git show flags as usual to overwrite it.

# a) Default
show
# b) Custom flags
show --compact-summary HEAD~1

untracked

Check for untracked files and directories that could be removed of current working directory.

Notes:

  • This command does git clean --dry-run -d only.
  • It doesn't remove anything, just makes a clean checking of files and directories that could be removed.
  • No flags are supported.
untracked
# Would remove .file1
# Would remove dir1/
# Would remove file2

commit

Commit changes to the repository.

Note: This command does git commit only. Add your git commit flags as usual to overwrite it.

commit
commit README.md
commit .
commit --amend

commit-all

Add and commit all changes to the repository.

Note: This command does stage and then commit .. No flags supported.

# stage && commit .
commit-all

tag

List and create release tag versions following The Semantic Versioning 2.0.0.

Show information about Tag options

tag -h                                                                                                                                          (13s 251ms)
# NAME
#       Gitnow: tag - List or tag commits following The Semantic Versioning 2.0.0 (Semver) [1]
#       [1] https://semver.org/
# EXAMPLES
#       List tags: tag
#       Custom tag: tag <my tag name>
#       Semver tag: tag --major
# OPTIONS:
#       Without options all tags are listed in a lexicographic order and tag names are treated as versions
#       -x --major         Tag auto-incrementing a major version number
#       -y --minor         Tag auto-incrementing a minor version number
#       -z --patch         Tag auto-incrementing a patch version number
#       -l --latest        Show only the latest Semver release tag version (no suffixed ones or others)
#       -h --help          Show information about the options for this command

List all available tags

Tags are listed in a lexicographic order and tag names are treated as versions.

tag

Get latest Semver release tag name

Note: This option gets only the latest Semver release version tag name but no any suffixed version ones or another kind of version names. The same apply when you create correlative Semver tags. See next section.

tag --latest

Create Semver correlative tag names

Note: Following commands take care about optional v prefixed tag names. So for example if a v1.0.0 is found as latest major then the next correlative tag name major will be v2.0.0. Otherwise for example if a 1.0.0 is found as latest minor then the next correlative tag name minor will be 1.1.0.

# Create a correlative Semver major tag
tag --major
# Create a correlative Semver minor tag
tag --minor
# Create a correlative Semver patch tag
tag --patch

Create custom tag names

tag <some tag name>

pull

Pull changes from remote server but saving uncommitted changes.

This command makes this for you:

  • Save your uncommitted changes locally using --autostash option.
  • Local changes you made will be rebased (---rebase option) on top of the remote changes.
  • Return your uncommitted changes locally again.

Auto mode:

  • pull
  • pull <branch_name>
  • pull <remote_origin> <branch_name>

Manual mode:

  • pull <remote_origin> <branch_name> --verbose
pull
๐Ÿ“ฅ Pulling changes
Arguments mode: Auto
Default arguments: --rebase --autostash
Remote: origin (https://github.com/joseluisq/gitnow.git)
Branch: master

From https://github.com/joseluisq/gitnow
 * branch            master     -> FETCH_HEAD
Created autostash: 473315a
HEAD is now at 9de2f93 update commands
Current branch master is up to date.
Applied autostash.

push

Push commit changes to remote repository.

Note: This command is equivalent to git push --set-upstream [your arguments...].

# Auto mode (current origin and branch)
push
# Manual mode
push <origin_name> <branch_name> <--some_other_flags>

upstream

Commit all changes and push them to remote server.

Note: This command does commit-all and then push. No flags supported.

upstream

move

Switch from current branch to another but stashing uncommitted changes

Note: This command does git stash then git checkout <other_branch> and finally git stash pop (possible to disable). It also takes care that <other_branch> matches with the existing local branches.

Additional options:

  • Use -u (or --upstream) flag to fetch a remote branch.
  • Use -n (or --no-apply-stash) flag to prevent stashed changes to be applied.
move other_branch

# Branch `ghost_branch` was not found. No possible to switch.
move ghost_branch

# With -u flag the branch will be fetched from remote origin.
move -u feature/new_remote_branch

# With -n flag stashed changes will not be applied.
move -n feature/new_remote_branch

# Possible to combine two option flags
move -un feature/another_remote_branch

merge

Merge a local branch into the active one

Note: This command does a simple git merge <other branch>.

Additional options:

  • Use -a (or --abort) flag instead of a branch name to abort a conflicted merge.
  • Use -c (or --continue) flag instead of a branch name to continue a merge.
merge other_branch

# Local branch ghost_branch was not found. Not possible to merge.
merge ghost_branch

# With -a flag the conflicted merge will be aborted.
merge -a

assume

Ignore changes in certain files temporarily.

Note: This command performs git update-index --[no-]assume-unchanged to ignore changes in certain files temporarily or revert those changes back.

Options:

  • -n --no-assume: No assume unchanged files to be ignored (revert option)
  • -h --help: Show information about the options for this command
# a) Ignore files temporarily
assume Cargo.toml README.md

# b) Revert file ignored changes
assume -n Cargo.toml README.md

feature

Creates a new feature (Gitflow) branch from current branch.

Note: Your new branch will always be lowercase without special characters or whitespaces (underscores instead).

feature feat1
# > feature/feat1
feature "This is my New FEATURE Branch"
# > feature/this_is_my_new_feature_branch

hotfix

Creates a new hotfix (Gitflow) branch from current branch.

Note: Your new branch will always be lowercase without special characters or whitespaces (underscores instead).

hotfix fix1
# > hotfix/fix1
hotfix "This is my New FIX Branch"
# > hotfix/this_is_my_new_fix_branch

bugfix

Creates a new bugfix (Gitflow) branch from current branch.

Note: Your new branch will always be lowercase without special characters or whitespaces (underscores instead).

bugfix fix1
# > bugfix/fix1
bugfix "This is my New bugFIX Branch"
# > bugfix/this_is_my_new_bugfix_branch

release

Creates a new release (Gitflow) branch from current branch.

Note: Your new branch will always be lowercase without special characters or whitespaces (underscores instead).

release fix1
# > release/fix1
release "This is my New release Branch"
# > release/this_is_my_new_bugfix_branch

logs

Shows logs in a fancy way.

Note: This command does git log HEAD by default using a pretty format. Add your git log flags as usual to overwrite it.

# shows all logs (default)
logs

# shows logs using git log parameters and flags (custom)
logs 8b09088
logs --before "yesterday" --after="1 week ago"

github

Clone a GitHub repository using SSH.

Examples:

github username/repo-name
github username repo-name

# requires a `user.github` username Git config entry
github repo-name

bitbucket

Clone a Bitbucket Cloud repository using SSH.

Examples:

bitbucket username/repo-name
bitbucket username repo-name

# requires a `user.bitbucket` username Git config entry
bitbucket repo-name

Note: For cloning some repo only, it's necessary to set your Github or Bitbucket username to global config before like:

# a) GitHub
git config --global user.github "your_username"
# b) Bitbucket
git config --global user.bitbucket "your_username"

Bonus

Contributions

Pull requests and issues are welcome.

License

MIT license

ยฉ 2016-present Jose Quintana

gitnow's People

Contributors

alexislefebvre avatar grafikart avatar horisakis avatar iillexial avatar jorgebucaran avatar joseluisq avatar lanzafame avatar lukasgierth avatar sirwrexes avatar xanderificnl avatar xasx avatar zerostats avatar

Stargazers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

Watchers

 avatar  avatar  avatar  avatar  avatar  avatar

gitnow's Issues

Add show command in order to show commit details

It would be great if we can support a command to show commit changes.

Proposal: I suggest to add a show command that performs git show --compact-summary HEAD by default which produces the following output in a compact way:

~> show
commit 10c403c9c7f7848d97d4896dc7fccb73daa5c6b0 (HEAD -> master, origin/master)
Author: Jose Quintana <jq@localhost>
Date:   Thu Feb 20 13:54:07 2020 +0100

    feat: some feature

 {src/lib => lib}/file.go                 |  0
 src/config/config.yml (new)              | 30 ++++++++++++++++++++++++++++++
 2 files changed, 30 insertions(+)

Variants

# 1. Automatic: display the current commit (HEAD) by default
#    It performs: `git show --compact-summary HEAD`
~> show

# 2. Manual: it can support all `git show` flags as well
~> show --compact-summary HEAD~1

Add tag command with Semver release support

Add tag command to create Git tags following The Semantic Versioning 2.0.0 and supporting the following options:

Proposal

# show all tags available
~> tag

# show all tag command flags
~> tag -h
-n --new-version [version]  tag a new version
-x --major                  tag auto-incrementing a major version number
-y --minor                  tag auto-incrementing a minor version number
-y --patch                  tag auto-incrementing a patch version number

Examples

~> tag --new-version v1.0.0
# v1.0.0
~> tag --major
# v2.0.0
~> tag --minor
# v2.1.0
~> tag --patch
# v2.1.1

'pull' does not pull tags in auto mode

Is there a reason why the 'pull' command does not also automatically pull the tags (in auto mode)?

I think it would make sense to always also fetch the tags when pulling in auto mode.

Upgrade command push to push all branches changes

Send all modifications on all branches by default.

Useful to push two branches changes or more branches changes or of course one branche changes

The Command:

git push <remote> --all

or better on all remotes using git remote -v command to detect the remotes

Best regards Willy Micieli

Tag command: add Semver pre-release support

Similar to #3 the tag command should support pre-releases.

Examples

~> tag --prerelease
# v2.1.1-0
~> tag --prerelease
# v2.1.1-1
~> tag --premajor
# v3.0.0-0
~> tag --preminor
# v3.1.0-0
~> tag --prepatch
# v3.1.1-0
~> tag --prerelease
# v3.1.1-1

[email protected] add unwanted entries into kubens and kubectx

After updating to 2.3.0, I noticed that I started seeing the following entries in kubens and kubectx (with fzf)

GitNow: Configured and ready to use!
GitNow: Downloading default configuration file...

If I downgrade back to 2.2.0 I do not see these entries. Fzf itself is not getting these extra GitNow entries; I've only noticed it with kubectx and kubens.

Send tags

You can also add a command send to push all tags.

git push <remote> --tags

Or better on all remotes using git remote -v command.

Best regard Willy Micieli

Add support to previous branch shorthand

Hi,

Can I request an enhancement for the move comand? I usually go between current and previous branch by using the - shorthand. Would you consider adding support for it?

~/ (master) $ move staging
~/ (staging) $ move -
~/ (master) $ 

Thank you!

Add support for ignoring file changes temporary

Ignoring files temporary is a useful feature when we need to quickly hide changes in a file(s) for awhile.

Using git update-index --[no-]assume-unchanged we can achieve this.

Proposal: I suggest to add an assume command in order to perform this.
The idea comes from this link.

  1. Ignoring files: Ignoring two files which contain changes (--assume-unchanged):
~> assume Cargo.toml README.md
# then `state` command should show us a clean working tree
~> state
Current working tree status:
## develop

Behind the scenes:

~> git update-index --assume-unchanged Cargo.toml README.md
  1. Revert ignored files: Reverting ignored files above via --no flag (--no-assume-unchanged):
~> assume --no Cargo.toml README.md
# then `state` command should show us changes in working directory
~> state
Current working tree status:
## master
M README.md
M Cargo.toml

Behind the scenes:

~> git update-index --no-assume-unchanged Cargo.toml README.md

Add untracked command in order to check for untracked files

It would be great if we can add support for untracked files checking on the working tree.

The way to do it, it's to use git clean with --dry-run which just check untracked files. -d is used for directories checking as well.

git clean --dry-run -d

Proposal: I suggest introduce an untracked command in order to perform this operation.

~> untracked
Would remove a
Would remove abc/
Would remove b
Would remove c

fisher with custom $fisher_path is not supported

Issue

gitnow assumes that fisher installs plugin into user's $__fish_config_dir. This is not always the case.
If a $fisher_path is used, the plugin fails to load and produces a lot of error messages on fish startup.

How to reproduce:

  1. Set $fisher_path to a custom path, e.g. ~/.local/share/fisher.
  2. Install fisher: curl ...
  3. Load $fisher_path/conf.d and add functions/completions to the appropriate paths in your own configuration as described in jorgebucaran/fisher#640.
  4. Try to install gitnow and observe the failure:
$ fisher install joseluisq/[email protected]
fisher install version 4.4.3
Fetching https://api.github.com/repos/joseluisq/gitnow/tarball/2.11.0
Installing joseluisq/[email protected]
           /home/liri/.local/share/fisher/functions/__gitnow_config_file.fish
           /home/liri/.local/share/fisher/functions/__gitnow_functions.fish
           /home/liri/.local/share/fisher/functions/__gitnow_manual.fish
           /home/liri/.local/share/fisher/conf.d/gitnow.fish
           /home/liri/.local/share/fisher/conf.d/gitnow_config.fish
           /home/liri/.local/share/fisher/completions/__gitnow_completions.fish
GitNow version  is installed and ready to use!
Just run the `gitnow` command if you want explore the API.
source: Error encountered while sourcing file '/home/liri/.config/fish/functions/__gitnow_functions.fish':
source: No such file or directory
source: Error encountered while sourcing file '/home/liri/.config/fish/functions/__gitnow_manual.fish':
source: No such file or directory
source: Error encountered while sourcing file '/home/liri/.config/fish/functions/__gitnow_config_file.fish':
source: No such file or directory
source: Error encountered while sourcing file '/home/liri/.config/fish/completions/__gitnow_completions.fish':
source: No such file or directory
Installed 1 plugin/s

I am pretty sure the issue is with gitnow_config.fish that tries to source fish functions directly. I am not sure why this is necessary.

Possible solutions

Check $fisher_path in gitnow_config.fish explicitly

Since $__fundle_plugins_dir is already queried in this file, checking $fisher_path could also be an option. This is how it looks on my PC after I install gitnow:

$ tree $fisher_path
/home/liri/.local/share/fisher
โ”œโ”€โ”€ completions
โ”‚ย ย  โ”œโ”€โ”€ fisher.fish
โ”‚ย ย  โ””โ”€โ”€ __gitnow_completions.fish
โ”œโ”€โ”€ conf.d
โ”‚ย ย  โ”œโ”€โ”€ gitnow_config.fish
โ”‚ย ย  โ””โ”€โ”€ gitnow.fish
โ”œโ”€โ”€ functions
โ”‚ย ย  โ”œโ”€โ”€ fisher.fish
โ”‚ย ย  โ”œโ”€โ”€ __gitnow_config_file.fish
โ”‚ย ย  โ”œโ”€โ”€ __gitnow_functions.fish
โ”‚ย ย  โ””โ”€โ”€ __gitnow_manual.fish
โ””โ”€โ”€ themes

Make gitnow functions fish autoload-compliant

Don't explicitly source gitnow functions, and rely on $fish_function_path and other autoloaders to correctly load your plugin.
For backward compatibility that can be done with something like set -q __gitnow_dont_autoload.

This will require splitting existing gitnow function files into multiple files, one file per gitnow function:

  • __gitnow_config_file.fish
    • __gitnow_read_config.fish
    • __gitnow_get_clip_program.fish
  • __gitnow_functions.fish
    • __gitnow_new_branch_switch.fish
    • __gitnow_slugify.fish
    • __gitnow_clone_repo.fish
    • __gitnow_clone_msg.fish
    • __gitnow_check_if_branch_exist.fish
    • __gitnow_clone_params.fish
    • __gitnow_gitflow_branch.fish
    • __gitnow_msg_not_valid_repository.fish
    • __gitnow_current_branch_name.fish
    • __gitnow_current_branch_list.fish
    • __gitnow_current_remote.fish
    • __gitnow_is_git_repository.fish
    • __gitnow_has_uncommited_changes.fish
    • __gitnow_get_latest_tag.fish
    • __gitnow_get_tags_ordered.fish
    • __gitnow_get_latest_semver_release_tag.fish
    • __gitnow_increment_number.fish
    • __gitnow_get_valid_semver_release_value.fish
    • __gitnow_get_valid_semver_prerelease_value.fish
    • __gitnow_is_number.fish

See how fish autoloads functions.

Move gitnow functions from functions to conf.d subdirectory

These functions will be loaded once by the plugin system, since conf.d is automatically sourced. And if these functions are ordered correctly, for example

  • conf.d/__10_gitnow_config_file.fish
  • conf.d/__10_gitnow_functions.fish
  • conf.d/__90_gitnow_config.fish -- make sure this file is sorted after functions it relies on

This approach is not idiomatic in fish, but it will load these functions correctly, and there is no more need to source functions/*.fish files.

my shell crashes when I try to install this

m@smolfrosty ~> fisher add joseluisq/gitnow
To completely erase z's data, remove:
/home/m/.local/share/z/data
fetching https://codeload.github.com/jethrokuan/z/tar.gz/HEAD
fetching https://codeload.github.com/jethrokuan/fzf/tar.gz/HEAD
fetching https://codeload.github.com/joseluisq/gitnow/tar.gz/HEAD
linking ~/.config/fish/functions/__z.fish
linking ~/.config/fish/functions/__z_add.fish
linking ~/.config/fish/functions/__z_clean.fish
linking ~/.config/fish/functions/__z_complete.fish
linking ~/.config/fish/conf.d/z.fish
linking ~/.config/fish/functions/__fzf_cd.fish
linking ~/.config/fish/functions/__fzf_complete.fish
linking ~/.config/fish/functions/__fzf_complete_preview.fish
linking ~/.config/fish/functions/__fzf_find_file.fish
linking ~/.config/fish/functions/__fzf_get_dir.fish
linking ~/.config/fish/functions/__fzf_open.fish
linking ~/.config/fish/functions/__fzf_parse_commandline.fish
linking ~/.config/fish/functions/__fzf_reverse_isearch.fish
linking ~/.config/fish/functions/__fzfcmd.fish
linking ~/.config/fish/conf.d/fzf.fish
linking ~/.config/fish/conf.d/fzf_key_bindings.fish
linking ~/.config/fish/functions/__gitnow_config_file.fish
linking ~/.config/fish/functions/__gitnow_functions.fish
~/.config/fish/functions/__gitnow_functions.fish (line 146): Unsupported use of '||'. In fish, please use 'COMMAND; or COMMAND'.
command git diff-index --quiet HEAD -- || echo "1" 2>&1
^
from sourcing file ~/.config/fish/functions/__gitnow_functions.fish
called on line 390 of file ~/.config/fish/functions/fisher.fish

in function '_fisher_add'
called on line 335 of file ~/.config/fish/functions/fisher.fish
with parameter list '/home/m/.local/share/fisher/github.com/joseluisq/gitnow'

in function '_fisher_fetch'
called on line 196 of file ~/.config/fish/functions/fisher.fish
with parameter list 'jethrokuan/z jethrokuan/fzf joseluisq/gitnow'

in command substitution
called on line 194 of file ~/.config/fish/functions/fisher.fish

in function '_fisher_commit'
called on line 91 of file ~/.config/fish/functions/fisher.fish
with parameter list 'add joseluisq/gitnow'

in function 'fisher'
called on standard input
with parameter list 'add joseluisq/gitnow'

linking ~/.config/fish/functions/__gitnow_manual.fish
linking ~/.config/fish/completions/__gitnow_completions.fish

below that last line it never finishes and I tried to ssh into it just now and the shell is broken

Last login: Fri Sep 11 15:48:10 2020 from 192.168.178.171
~/.config/fish/functions/__gitnow_functions.fish (line 146): Unsupported use of '||'. In fish, please use 'COMMAND; or COMMAND'.
command git diff-index --quiet HEAD -- || echo "1" 2>&1
^
from sourcing file ~/.config/fish/functions/__gitnow_functions.fish
called on line 13 of file ~/.config/fish/conf.d/gitnow_config.fish

from sourcing file ~/.config/fish/conf.d/gitnow_config.fish
called on line 250 of file /usr/share/fish/config.fish

from sourcing file /usr/share/fish/config.fish
called during startup

source: Error while reading file '/home/m/.config/fish/functions/__gitnow_functions.fish'

fisher: Plugin not supported: "joseluisq/gitnow"

Hi!

I get the following message when installing gitnow with fisher:

โฏ fisher install joseluisq/gitnow
fisher install version 4.2.0
Fetching https://codeload.github.com/joseluisq/gitnow/tar.gz/HEAD
fisher: Plugin not supported: "joseluisq/gitnow"
Support for .fish files outside a functions directory is deprecated https://github.com/jorgebucaran/fisher/issues/651

How do I avoid that?

Thanks!

Add support for ignore files persistently

It would be great if we can support a command to ignore (or revert) files on demand and place them into .gitignore file.

Proposal: I suggest to add an ignore command.

1. Ignore a file:

~> ignore README.md
~> cat .gitignore
# README.md

1. Revert ignored file:

~> ignore --no README.md
~> cat .gitignore
# (empty)

Slow startup

source $__fish_data_dir/completions/git.fish in __gitnow_completions.fish seems to cause my start up to be really slow. After commenting out this line, it starts up just fine

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    ๐Ÿ–– Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. ๐Ÿ“Š๐Ÿ“ˆ๐ŸŽ‰

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google โค๏ธ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.