<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:sy="http://purl.org/rss/1.0/modules/syndication/" xmlns:media="http://search.yahoo.com/mrss/"><channel><title>Git on Shaowen Chen's Website</title><link>https://www.chenshaowen.com/en/tags/git/</link><description>Recent content in Git on Shaowen Chen's Website</description><generator>Hugo -- gohugo.io</generator><language>en</language><copyright>&amp;copy;2016 - {year}, All Rights Reserved.</copyright><lastBuildDate>Mon, 22 Jun 2020 00:00:00 +0000</lastBuildDate><sy:updatePeriod>weekly</sy:updatePeriod><atom:link href="https://www.chenshaowen.com/en/tags/git/atom.xml" rel="self" type="application/rss+xml"/><item><title>Analyzing the Lightweight Checkout Problem in Jenkins</title><link>https://www.chenshaowen.com/en/blog/the-question-of-lightweight-checkout-in-jenkins.html</link><pubDate>Mon, 22 Jun 2020 00:00:00 +0000</pubDate><atom:modified>Mon, 22 Jun 2020 00:00:00 +0000</atom:modified><guid>https://www.chenshaowen.com/en/blog/the-question-of-lightweight-checkout-in-jenkins.html</guid><description>1. What Problem We Hit A Jenkins build log threw an error:
1 2 3 4 5 6 Started by user admin Lightweight checkout support not available, falling back to full checkout. Checking out git https://github.com/shaowenchen/pipeline-test.git into /var/jenkins_home/workspace/abc@script to read Jenkinsfile ... ... Unable to access &amp;#39;.git/index.lock&amp;#39;: File exists. Cause analysis:</description><dc:creator>微信公众号</dc:creator><category>Jenkins</category><category>Git</category><category>DevOps</category><category>Troubleshooting</category></item><item><title>Git Tips You Didn't Know</title><link>https://www.chenshaowen.com/en/blog/git-skills-you-do-not-notice.html</link><pubDate>Fri, 17 May 2019 00:00:00 +0000</pubDate><atom:modified>Fri, 17 May 2019 00:00:00 +0000</atom:modified><guid>https://www.chenshaowen.com/en/blog/git-skills-you-do-not-notice.html</guid><description>1. Pages GitHub, GitLab, Bitbucket and others all offer a free static page hosting service called Pages. With the Pages service you can publish documentation, blogs, and more. Taking GitHub as an example, using Pages usually takes just a few simple steps: Create a new project: [username].github.io Commit static html</description><dc:creator>微信公众号</dc:creator><category>Tips</category><category>Git</category><category>Processes</category><category>Development</category><category>R&amp;D</category></item><item><title>Git and Development Environment Setup</title><link>https://www.chenshaowen.com/en/blog/git-and-development-environment-setup.html</link><pubDate>Fri, 19 Oct 2018 00:00:00 +0000</pubDate><atom:modified>Fri, 19 Oct 2018 00:00:00 +0000</atom:modified><guid>https://www.chenshaowen.com/en/blog/git-and-development-environment-setup.html</guid><description>Compiled from the &amp;ldquo;Development Tips&amp;rdquo; series, gathering practices around Git collaboration and development environment setup. 1. warning: LF will be replaced by CRLF Windows, Linux, and Mac are inconsistent in how they mark line endings in files. Windows uses CRLF as the terminator, while Linux and Mac use LF. Git</description><dc:creator>微信公众号</dc:creator><category>Git</category><category>Python</category><category>Windows</category><category>R&amp;D</category><category>Environment</category></item><item><title>Common Git Commands</title><link>https://www.chenshaowen.com/en/blog/common-git-commands.html</link><pubDate>Mon, 18 Dec 2017 11:22:55 +0000</pubDate><atom:modified>Mon, 18 Dec 2017 11:22:55 +0000</atom:modified><guid>https://www.chenshaowen.com/en/blog/common-git-commands.html</guid><description>1. Basic Concepts Workspace: the working area, the project files Index: the staging area, also called the pending-commit area; before a commit enters the repo, all updates are placed in the staging area Local Repository: the local repo, the version repository kept locally; HEAD points at the current development branch</description><dc:creator>微信公众号</dc:creator><category>Git</category><category>Tools</category><category>Version Control</category><category>Command Line</category><category>R&amp;D</category></item><item><title>A Successful Git Branching Model</title><link>https://www.chenshaowen.com/en/blog/a-successful-git-branching-model.html</link><pubDate>Sun, 04 Dec 2016 20:34:03 +0000</pubDate><atom:modified>Sun, 04 Dec 2016 20:34:03 +0000</atom:modified><guid>https://www.chenshaowen.com/en/blog/a-successful-git-branching-model.html</guid><description>This article is built around Git, the tool that controls all of our source code.
1. Why Git? For an in-depth discussion of the pros and cons of git versus centralized source control systems, see here. There has been far too much heated argument on this subject. As a developer, I currently prefer Git over other tools.</description><dc:creator>微信公众号</dc:creator><category>Translation</category><category>Tools</category><category>Git</category><category>R&amp;D</category><category>Branching Model</category></item></channel></rss>