Pro Git 2nd Edition 2.1.413or files produced by your build system. In such cases, you can create a file listing patterns to match them named .gitignore. Here is an example .gitignore file: $ cat .gitignore *.[oa] *~ The first character between them (in this case 0 through 9). You can also use two asterisks to match nested directories; a/**/z would match a/z, a/b/z, a/b/c/z, and so on. Here is another example .gitignore file: # ignore relative date such as "2 years 1 day 3 minutes ago". You can also filter the list to commits that match some search criteria. The --author option allows you to filter on a specific author, and the --0 码力 | 731 页 | 21.49 MB | 1 年前3
Pro Git 2nd Edition 2.1.413or files produced by your build system. In such cases, you can create a file listing patterns to match them named .gitignore. Here is an example .gitignore file: $ cat .gitignore *.[oa] *~ The first character between them (in this case 0 through 9). You can also use two asterisks to match nested directories; a/**/z would match a/z, a/b/z, a/b/c/z, and so on. 32 Here is another example .gitignore file: relative date such as "2 years 1 day 3 minutes ago". 44 You can also filter the list to commits that match some search criteria. The --author option allows you to filter on a specific author, and the --grep0 码力 | 501 页 | 17.96 MB | 1 年前3
Pro Git 2nd Edition 2.1.413 or files produced by your build system. In such cases, you can create a file listing patterns to match them named .gitignore. Here is an example .gitignore file: $ cat .gitignore *.[oa] *~ The first character between them (in this case 0 through 9). You can also use two asterisks to match nested directories; a/**/z would match a/z, a/b/z, a/b/c/z, and so on. Here is another example .gitignore file: # ignore relative date such as "2 years 1 day 3 minutes ago". You can also filter the list to commits that match some search criteria. The --author option allows you to filter on a specific author, and the --0 码力 | 691 页 | 13.35 MB | 1 年前3
Pro Git 中文版 第2版 2.1.66的关键字。 你可以指定多个 --author 和 --grep 搜索条件,这样会只输出匹配 任意 --author 模式和 任意 --grep 模式的提交。然而,如果你添加了 --all-match 选项, 则只会输出匹配 所有 --grep 模式的提交。 另一个非常有用的过滤器是 -S(俗称“pickaxe”选项,取“用鹤嘴锄在土里捡石头”之意), 它接受一个字 符串参数,并且只会显示那些添加或删除了该字符串的提交。 push["commits"].each do |commit| # look for a Signed-off-by string if /Signed-off-by/.match commit['message'] state = 'success' description = 'Successfully signed off!' else &now_tm)) date.c:545: if (gmtime_r(&time, tm)) { date.c:758: /* gmtime_r() in match_digit() may have clobbered it */ git-compat-util.h:1138:struct tm *git_gmtime_r(const time_t *, struct0 码力 | 501 页 | 19.30 MB | 1 年前3
Pro Git 中文版 第2版 2.1.66选项搜索提交说明中的关键字。 你可以指定多个 --author 和 --grep 搜索条件,这样会只输出匹配 任意 --author 模式和 任 意 --grep 模式的提交。然而,如果你添加了 --all-match 选项, 则只会输出匹配 所有 -- grep 模式的提交。 另一个非常有用的过滤器是 -S(俗称“pickaxe”选项,取“用鹤嘴锄在土里捡 石头”之意), 它接受一个字符串参数,并且只会显示那些添加或删除了该字 push["commits"].each do |commit| # look for a Signed-off-by string if /Signed-off-by/.match commit['message'] state = 'success' description = 'Successfully signed off!' else &now_tm)) date.c:545: if (gmtime_r(&time, tm)) { date.c:758: /* gmtime_r() in match_digit() may have clobbered it */ git-compat-util.h:1138:struct tm *git_gmtime_r(const time_t *, struct0 码力 | 670 页 | 13.59 MB | 1 年前3
Gitea v1.21.1 中文文档认证。这可以通过利用 SSH AuthorizedKeysCommand 来匹配 Gitea 接受的密钥。在主机的 /etc/ssh/sshd_config 文件中添加以下代码 块: 1. Match User git 2. AuthorizedKeysCommandUser git 3. AuthorizedKeysCommand /usr/bin/docker exec -i @org/team]... Regexp specified in golang Regex format. Regexp can start with ! for negative rules - match all files except specified. Example file: 1. .*\\.go @user1 @user2 # This is comment 2. 3. #0 码力 | 303 页 | 3.88 MB | 1 年前3
共 6 条
- 1













