gitkraken

Linux 基础自学笔记(三)常用文件目录类操作指令

て烟熏妆下的殇ゞ 提交于 2019-12-18 22:12:25
Linux文件目录类指令 1. pwd: pwd 命令用于查询当前所在路径(绝对路径): 2. ls: ls 命令用于查看当前目录下的文件及文件夹: ls 常用参数: -a :查看全部文件及目录,包括隐藏文件和目录,在Linux中隐藏文件或目录前面均带有一个“.”。 -l:以列表/清单的形式查看当前目录下的文件或文件夹: 3. cd cd 命令用于目录切换,要切换到上级的目录及其子目录时,需要使用绝对路径,切换到当前目录的下级目录时,可以使用相对路径。 要返回上一级目录,可使用 cd … 命令,若要向上返回多级,需以/分割 :cd …/…/… 要切换到用户的主目录时,可使用 cd ~ 命令。 要切换到根目录时,可使用 cd /。 4. mkdir mkdir 指令用于创建目录: mkdir指令,默认只可以创建一级目录,若要创建多级目录,需加上参数 -p: 5. rmdir: mkdir 指令用于删除空目录,若指定路径非空,则系统会返回错误信息: 6. rm: rm 指令用于删除一个文件或者目录: rm 常与 -rf参数连用, -r:递归 -f:force 语法:rm -rf 文件/目录 7. touch: 文件创建命令,用来创建一个空文件: 语法: touch filename: 8. cp: 文件拷贝命令,用于文件/目录的复制操作: 相当于在源路径下复制

(GitKraken) Pre-commit Failed Exit Code: 1

自古美人都是妖i 提交于 2019-12-13 05:38:42
问题 I'm using GitKraken (not sure if relevant) and as I'm trying to commit, I get this error message: And as I press the button "View Hook Output" I get the following: pre-commit husky > npm run -s precommit (node v8.9.4)[?25l npm > Running tasks for src/**/*.js \ yarn format git add (...lots of these two rows...) \ yarn format git add "yarn format" found some errors. Please fix them and try committing again. yarn run v1.6.0 $ prettier-standard './src/**/*.js' C:\mypath\myfile.js info[Visit [0

Git hook pre-push prompt to squash commits first

自闭症网瘾萝莉.ら 提交于 2019-12-11 14:36:32
问题 I'm not sure if I'm going about this the correct way. Sorta new to Git and GitKraken. I want to force others to squash their feature branch commits before pushing and creating a pull request. So I've tried the following pre-push git hook but even when I squash first it still thinks there are multiple commits. What am I missing? Thanks! #!/bin/sh # An example hook script to verify what is about to be pushed. Called by "git # push" after it has checked the remote status, but before anything has

How to add a remote to a repository with lfs?

本秂侑毒 提交于 2019-12-08 01:32:23
问题 I'm trying to set up something like this: a bare repo on my HDD drive and a clone of it on my SSD with lfs installed. I'm doing it like this: First I set up a bare repo on my HDD: mkdir git_lfs_test.git cd git_lfs_test.git git init --bare And then on my SSD: git clone D:/Git/git_lfs_test.git cd git_lfs_test git lfs install git lfs track '*.png' After doing this I open the cloned repo in GitKraken. I make the initial commit and then commit and push the .gitattributes file. Then I create a png

How to add a remote to a repository with lfs?

喜你入骨 提交于 2019-12-06 07:29:12
I'm trying to set up something like this: a bare repo on my HDD drive and a clone of it on my SSD with lfs installed. I'm doing it like this: First I set up a bare repo on my HDD: mkdir git_lfs_test.git cd git_lfs_test.git git init --bare And then on my SSD: git clone D:/Git/git_lfs_test.git cd git_lfs_test git lfs install git lfs track '*.png' After doing this I open the cloned repo in GitKraken. I make the initial commit and then commit and push the .gitattributes file. Then I create a png file (which GitKraken recognises as a lfs file) and push it to the origin. It throws this error: Remote

GitKraken config file (Windows)

孤者浪人 提交于 2019-12-05 02:58:57
Where can I find the config files for GitKraken on Windows? GitKraken shows many repositories, which I would not like to be listed in the "recently opened repos" list. GitKraken saves its configuration in %AppData%/.gitkraken . Despite missing a file ending, all files here are JSON, so you can open them directly in a text editor. config for instance seems to store general settings such as window location and size. You can remove a repo from "recently opened repos" by removing it from the localRepoCache in the profiles/<random string>/ subfolder. 来源: https://stackoverflow.com/questions/37678725

How to checkout commit in GitKraken?

早过忘川 提交于 2019-12-03 14:27:59
问题 It seems to be impossible to checkout commits with GitKraken. As you can see there is no option to checkout older commits, only Cherrypick commit but I don't know what this is good for. EDIT: I was able to checkout with another git program (git bash) via console: Now it looks like this in GitKraken: 回答1: GitKraken (as of version 1.7) does not seem to offer a way to get into a detached HEAD mode, and check out a commit directly. Similarly, it will also not allow you to check out a tag (since

Gitkraken Desktop App - Error login: “Please log in to continue”

醉酒当歌 提交于 2019-12-03 08:16:40
问题 Who has been working with client GitKraken as GIT, you will know that authentication required? For the application, log in with: firstemail@outlook.com The repository is with: businessemail@bussiness.com It requires credentials to make a pull, but I tried with both emails and usernames, and does not allow me. Capture: In SourceTree it works perfectly, but here not!. Thanked fully!. 回答1: The credentials asked for, are the credentials for the repo you are trying to access, not for your

GitKraken And Github - failed to get server certificate: The handle is in the wrong state for the requested operation

妖精的绣舞 提交于 2019-12-03 06:52:05
I am getting this error message from GitKraken whenever I try to clone/fetch/push/push to any of my Github repositories: failed to get server certificate: The handle is in the wrong state for the requested operation I have no idea why this is happening, everything was working fine with my current setup until yesterday and I have checked that GitKraken is properly authorized to connect to my Github account and my repositories. What I have tried: Remove and add my credentials, reauthorize GitKraken. Check my Git installation - can correctly push/pull and clone Github repos. Tested on another

How to checkout commit in GitKraken?

牧云@^-^@ 提交于 2019-12-03 04:14:15
It seems to be impossible to checkout commits with GitKraken. As you can see there is no option to checkout older commits, only Cherrypick commit but I don't know what this is good for. EDIT: I was able to checkout with another git program (git bash) via console: Now it looks like this in GitKraken: GitKraken (as of version 1.7) does not seem to offer a way to get into a detached HEAD mode, and check out a commit directly. Similarly, it will also not allow you to check out a tag (since that would also give you a detached HEAD). So instead, you will have to create a (temporary) branch first