-
Local projects are uploaded to GitHub via GIT Download git installation by default, and then open git bash first installation configuration in the menu bar to configure the mailbox with the same account name git config --global user.name “Your_github-Username” git config --global user.email “Your_github-email” #View user name mailbox git config user.name git config user.email #You can also view the user's mailbox directly vim ~/.gitconfig : Q exit to create SSH key. Since the transmission between local git warehouse and GitHub warehouse is encrypted through SSH, you need to set it when connecting. First, check whether there is a. SSH directory in the user directory of disk C. if there is a hidden (C: users user name), check whether. SSH has a private key ID_ RSA and public key ID_ If there are rsa.pub files, you can skip to the next step. If not, create SSH keygen - t RSA - C "your GitHub email" by following the command. Enter the carriage several times and set SSH key to log in to GitHub new SSH key title. For example: ID generated by gitkey: ID_ Create empty warehouse by rsa.pub (for uploading) https://github.com/new Other commands git RM - R -- cached. Delete all files in the cache (note that if there is a space, if you change. To a file name, it will cancel a file) git upload remote warehouse is empty (new warehouse, no readme. MD) 1. CD to the directory to be uploaded (local warehouse), such as the test folder, PWD can view the current location. 2. Initialize the local warehouse git init. A. Git folder will be created under the current test directory, which means that this folder will be changed into a git manageable warehouse. It is used by git to track and manage the version library. 3. Associate the remote warehouse git remote add origin GitHub warehouse HTTPS address. 4. Add files to the cache area git add. / / all contents in the current directory Git add user / / specify a file or folder Git status / / view cache file (note that there is a space in the ".", which means that all the files in this folder are submitted. You can also submit the specified files through the GIT add file name. 5. The comment content of this submission is in quotation marks after git commit - M 'first commit' - M. if you don't fill in, an error will be reported. 6. Upload the branch git branch XXX / / create a branch Git branch - A / / view branch Git checkout XXX / / switch branches Git push - U origin master remote warehouse is empty, so add - U parameter, the cached file is pushed to the master branch of GitHub warehouse, and the remote warehouse is not empty (old warehouse, including the warehouse with no content and record) 1. Clone remote warehouse (download) Git clone repository address 2. CD to the cloned warehouse ➽ the cloned warehouse contains the. Git folder, so it is not necessary to initialize git init and associate the remote warehouse address. 3. Add files to the cache git add. / / all contents in the current directory Git add user / / specify a file or folder Git status / / view cache file 4. Submit instruction git commit - M 'first commit' 5. Upload git push origin master to delete the warehouse file ▶ Delete git clone warehouse address locally and remotely //There is something to ignore Git RM file / / will be deleted locally Git RM - R folder / / will be deleted locally Git RM - RF. / / all local files will be deleted Git commit - M 'delete a file' Git push origin master will also delete the corresponding local file. If you do not want to delete the local file but only delete the corresponding part in the cache, add -- cached ▶ Delete remote warehouse git clone warehouse address only //There is something to ignore Git RM -- cached file / / will not be deleted locally Git RM - R -- cached folder / / will not be deleted locally Git RM - RF -- cached. / / all local files will not be deleted Git commit - M 'delete a file' git push origin master -
Discovery navigation deployment tutorial - GitHub page Recently, we found a good website navigation in GitHub, which is pure static, automatic deployment, appearance and simplicity coexist. It is no longer the era of killing Matt. More information can be found on GitHub. Here we record the detailed deployment process. Nav.ka.mk - this is what I built https://github.com/xjh22222228/nav How to deploy? It is recommended that you use GitHub pages service, so that you do not need to provide a server, and the project has its own automated deployment services. 1： First of all, one copy of fork is in its own warehouse. Second: apply for token. Check all of them. Otherwise, you have no permission. https://github.com/settings/tokens 3： [setting] – [secrets] [new secret] fill in the token just applied, and the name must be filled in token in capital four: [actions] - click [I understand my workflow, go ahead and enable them]! GitHub page find GitHub page in the settings, select GH pages branch and folder root to save. Now you can see the access address. After a while, you will be prompted that the domain name nav.xiejiahe.com is used. If you do not need to bind the domain name, you can delete the CNAME in the GH pages branch or modify it to your own. Submit commit to edit the "unimportant" file under the master branch of the main branch, such as readme.md, and save to trigger the action! Action has finished building and is now accessible. Modify the configuration file of the navigation data directory dataconfig / index.ts. The address on line 23 is the GIT address in the upper right corner. It is recommended to keep the Src / APP / app.component.html bottom footersrc / view / app.component.html mobile phone top link, logo address Src / index.html website name, statistical code assets / icon / logo.pnglogo. Node.js needs to be installed for local construction, Please refer to this article to record the source code of node.js/vue/yarn installation ා #Enter the directory C:\user>cd *\nav-master\nav-master #Installation dependency npm install #Compiling npm run build #Start The NPM start start prompt can be opened, http://localhost:port port
