sdttttt / gcr Goto Github PK

考虑到每个人的习惯, 我建议多加一些命令选项.

如下:

grc push <file_name> # 自动Add 该文件到index, 输入commit 信息,自动推送,  如果 file_name 是`.` 那么自动添加所有文件

grc add <file_name> # 自动Add 该文件到index, 输入commit 信息, 如果 file_name 是`.` 那么自动添加所有文件

I noticed that there is a lack of workflow for other platforms.

encounter an error when i run cargo install grc

error: failed to compile `grc v1.2.0`, intermediate artifacts can be found at `/tmp/cargo-installBHdw34`

Caused by:
  failed to select a version for the requirement `zeroize = "^0.9.3"`
  candidate versions found which didn't match: 1.3.0, 1.2.0, 1.1.1, ...
  location searched: crates.io index
  required by package `dialoguer v0.7.1`
      ... which is depended on by `grc v1.2.0`

By default, if signingKey is specified in ~/.gitconfig, git will automatically sign the commit using gpg. But when using grc, commits are not signed.

git log --show-signature

My gitconfig:

mgt in ~
❯ cat .gitconfig
[user]
    name = mgt
    email = [email protected]
    signingKey = 7965BF43A2143DD26F1A4850362C4BEE95C1C2DF
[commit]
    gpgSign = true

I've searched git2's document, and I guess it is possible to implement this feature. See https://docs.rs/git2/0.13.17/git2/struct.Repository.html#method.commit_signed .

Steps to reproduce

1. git init
2. touch README.md, git add README.md
3. grc, then failed

❯ grc
✔ Which scope? (Optional) ·
✔ Commit Message ? · 1st commit
✔ Provide a longer description? (Optional) ·
✔ PR & Issues this commit closes, e.g 123: (Optional) ·
GRC: feat: 1st commit
GRC: reference 'refs/heads/master' not found

Environments

• grc version: v1.0.0 from release page. grc --version GRC 1..0.0.beta.1
• git version: 2.30.1
• OS: macOS 10.14.6

Add configuration files belonging to grc to the warehouse file, through which some actions of grc can be changed.

An action that can be changed through a configuration file.

• Customize the submission type and scope.

This problem will be solved, such as the hook cannot be executed on the windows and the execution error is not clear.

I have updated this in the plugin description. Details: https://github.com/sdttttt/gcr/tree/master/src/plugins

Hi, your readme/about page mentions that grc is a temporary name. Is it likely to change in the near future?

I am developing a new crate that I'd hoped to use the name grc for. I'm happy to change the name as it's still very much a work in progress but if this will be changing soon I'll leave it as it is.

Thanks and good luck with the project.

I use direnv to export env GIT_AUTHOR_NAME, GIT_AUTHOR_EMAIL ... in specific directory to change author and committer. Seems these environment variables are not used.

I'm really not very good at TDD development...

• Unit test coverage to 15%

We can add an action hook to implement some additional operations, such as routine unit testing.

They may occur around the COMMIT.

Git already provides these capabilities, but they can be inconvenient to use.
https://git-scm.com/book/en/v2/Customizing-Git-Git-Hooks

Maybe I missed part of it. If the type of the grc.toml clock does not use symbols to separate types and descriptions, something unexpected will probably happen.

gcr or grc ? I'm not pretty sure which one is correct...

link is https://aur.archlinux.org/packages/git-grc/

• specifications Commit.

Currently, GRC locks grc.toml as a configuration file.

Hi, the pre-hooks may change the tracked files, while the gcr won't track these changes.

For example, when cargo fmt is hooked, I observe these:

Here is the configuration:

emoji = true
pre = ["cargo fmt"]
after = []

Pretty self-explanatory. Another idea is to force creation of it in a default folder, like ~/.config/grc/gcr.toml

In some cases, you may want a submission message to be reused over and over again.
(for example, when a locally built dist must be submitted to the warehouse)