blocks|key|1564070|text|“叉子”不是Git概念。你是把吉特和吉顿搞混了吗？如果你的意思是在Github上分叉这个项目，那就和克隆回购一样，克隆听起来就像你想要的一样。你永远不会把改变推回“样板”回购。但是，您可以使用合并或重基将样板回购的更新引入到从中派生出来的项目中。如果没有这样的东西是可取的，那为什么还要用Git呢？只需创建目录的递归副本，然后从那里开始。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1564071|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

"Fork" isn't a Git concept. Are you confusing Git with Github? If you mean forking the project on Github, then it's the same as cloning the repo, and cloning sounds like what you're looking for. You'd just never push changes back to the "boilerplate" repo. You could, however use merging or rebasing to pull in updates to the boilerplate repo into the projects that spin off of it. If nothing like that is desirable, then why even do it with Git? Just make a recursive copy of the directory, and start from there.

blocks|key|244550|text|更新2019年6月，6年后：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|244551|见"使用存储库模板生成新的存储库“|offset|length|244552|在软件开发中，在代码库之间共享样板代码是一种不变的模式。
用我们最喜欢的工具和目录结构引导一个新项目，可以帮助程序员从idea转向“Hello！”效率更高，手动配置更少。
今天，我们很高兴引入存储库模板，使样板代码管理和发行成为GitHub.上的头等公民。
首先，只需将存储库标记为模板，您就可以立即使用它生成新的存储库，并包含所有模板存储库的文件和文件夹。|blockquote|style|BOLD|244553|​|244554|📷|atomic|244555|244556|每个模板存储库都有一个名为/generate的新URL端点，它允许您更有效地分发模板|CODE|244557|2013年原始答复：|244558|考虑到您将从boilerplate+Github项目中包含的一个模板中存储您的项目，我会：|244559|在GitHub上创建一个新的空回购(没有与boilerplate的链接，没有需要叉子)|unordered-list-item|244560|克隆它|244561|在磁盘上的单独位置克隆boilerplate|244562|将正确的模板从本地boilerplate克隆复制到新的本地克隆的Github。|244563|(git+add，git+commit)将这个特定的模板推回给你的新的Github。|244564|从那里开始工作|244565|entityMap|0|LINK|mutability|MUTABLE|url|https://github.blog/2019-06-06-generate-new-repositories-with-repository-templates/|1|IMAGE|IMMUTABLE|imageUrl|https://developer.qcloudimg.com/http-save/yehe-900000/c85f4f8a2f02526255c81eeb90ec6460.gif|imageAlt|2|https://stackoverflow.com/questions/9257533/what-is-the-difference-between-origin-and-upstream-in-github/9257901#9257901^0|0|2|E|0|0|2H|W|0|0|0|1|1|0|0|D|9|N|J|D|9|0|0|A|0|0|19|6|B|0|0|17|L|B|12|4|2|0|0|3|0|0|M|B|B|0|0|13|9|B|0|0|16|1|7|9|A|0|0|7|0^^$0|@$1|2|3|4|5|6|7|1Q|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|1R|8|@]|9|@$D|1S|E|1T|1|1U]]|A|$]]|$1|F|3|G|5|H|7|1V|8|@$D|1W|E|1X|I|J]]|9|@]|A|$]]|$1|K|3|L|5|6|7|1Y|8|@]|9|@]|A|$]]|$1|M|3|N|5|O|7|1Z|8|@]|9|@$D|20|E|21|1|22]]|A|$]]|$1|P|3|L|5|6|7|23|8|@]|9|@]|A|$]]|$1|Q|3|R|5|H|7|24|8|@$D|25|E|26|I|J]|$D|27|E|28|I|J]|$D|29|E|2A|I|S]]|9|@]|A|$]]|$1|T|3|U|5|6|7|2B|8|@$D|2C|E|2D|I|J]]|9|@]|A|$]]|$1|V|3|W|5|6|7|2E|8|@$D|2F|E|2G|I|J]|$D|2H|E|2I|I|S]]|9|@]|A|$]]|$1|X|3|Y|5|Z|7|2J|8|@$D|2K|E|2L|I|J]|$D|2M|E|2N|I|S]]|9|@$D|2O|E|2P|1|2Q]]|A|$]]|$1|10|3|11|5|Z|7|2R|8|@$D|2S|E|2T|I|J]]|9|@]|A|$]]|$1|12|3|13|5|Z|7|2U|8|@$D|2V|E|2W|I|J]|$D|2X|E|2Y|I|S]]|9|@]|A|$]]|$1|14|3|15|5|Z|7|2Z|8|@$D|30|E|31|I|J]|$D|32|E|33|I|S]]|9|@]|A|$]]|$1|16|3|17|5|Z|7|34|8|@$D|35|E|36|I|J]|$D|37|E|38|I|S]|$D|39|E|3A|I|S]]|9|@]|A|$]]|$1|18|3|19|5|Z|7|3B|8|@$D|3C|E|3D|I|J]]|9|@]|A|$]]|$1|1A|3|-4|5|6|7|3E|8|@]|9|@]|A|$]]]|1B|$1C|$5|1D|1E|1F|A|$1G|1H]]|1I|$5|1J|1E|1K|A|$1L|1M|1N|-4]]|1O|$5|1D|1E|1F|A|$1G|1P]]]]

Update June 2019, 6 years later:

See "<a href="https://github.blog/2019-06-06-generate-new-repositories-with-repository-templates/" rel="noreferrer">Generate new repositories with repository templates </a>"

<blockquote>
 Sharing boilerplate code across codebases is a constant pattern in software development. 
 Bootstrapping a new project with our favorite tools and directory structures helps programmers go from idea to “Hello world!” more efficiently and with less manual configuration.
 
 Today, we’re excited to introduce repository templates to make boilerplate code management and distribution a first-class citizen on GitHub. 
 
 To get started, all you need to do is mark a repository as a template, and you’ll immediately be able to use it to generate new repositories with all of the template repository’s files and folders.
</blockquote>

<a href="https://i.stack.imgur.com/R4Kg0.gif" rel="noreferrer"><img src="https://i.stack.imgur.com/R4Kg0.gif" alt="https://github.blog/wp-content/uploads/2019/06/repository-template.gif"></a>

<blockquote>
 Every template repository gets a new URL endpoint called <code>/generate</code> that allows you to distribute your template more efficiently
</blockquote>

<hr>

Original answer 2013:

Considering you will be storing your project on Github from one of the templates included in <code>boilerplate</code> GitHub project, I would:

<ul>
<li>Create a new empty repo on GitHub (no link with <code>boilerplate</code>, no <a href="https://stackoverflow.com/questions/9257533/what-is-the-difference-between-origin-and-upstream-in-github/9257901#9257901">need for a fork</a>)</li>
<li>clone it</li>
<li>clone <code>boilerplate</code> in a separate location on your disk</li>
<li>copy the right template from the local <code>boilerplate</code> clone to your new locally cloned Github repo</li>
<li>(<code>git add</code>, <code>git commit</code>) Push that specific template back to your new Github repo.</li>
<li>start working from there</li>
</ul>

blocks|key|244642|text|@VonC的回答没有什么问题，但您可以使用网络中心创建一个基于种子回购(本地和远程)的新回购(本地和远程)有效的一条龙：|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|244643|clonefork()+{
++++hub+clone+"$1"
++++cd+"${1##*/}"
++++hub+fork
}|code-block|syntax|javascript|244644|在你的壳里：|244645|$+clonefork+user/seed-repo|244646|通过“克隆叉”您的种子回购，您还可以得到网络图显示所有的repos产生的。|244647|entityMap|0|LINK|mutability|MUTABLE|url|https://hub.github.com/|1|https://github.com/github/hub/issues/348#issuecomment-21292460|2|https://github.com/blog/39-say-hello-to-the-network-graph-visualizer^0|L|4|0|1K|3|1|0|0|0|0|K|3|2|0^^$0|@$1|2|3|4|5|6|7|10|8|@]|9|@$A|11|B|12|1|13]|$A|14|B|15|1|16]]|C|$]]|$1|D|3|E|5|F|7|17|8|@]|9|@]|C|$G|H]]|$1|I|3|J|5|6|7|18|8|@]|9|@]|C|$]]|$1|K|3|L|5|F|7|19|8|@]|9|@]|C|$G|H]]|$1|M|3|N|5|6|7|1A|8|@]|9|@$A|1B|B|1C|1|1D]]|C|$]]|$1|O|3|-4|5|6|7|1E|8|@]|9|@]|C|$]]]|P|$Q|$5|R|S|T|C|$U|V]]|W|$5|R|S|T|C|$U|X]]|Y|$5|R|S|T|C|$U|Z]]]]

Nothing wrong with @VonC's answer, but you can alternatively use <a href="https://hub.github.com/" rel="nofollow">hub</a> to create <a href="https://github.com/github/hub/issues/348#issuecomment-21292460" rel="nofollow">a one-liner</a> that effectively inits a new repo (locally and remotely) based on your seed repo:

<pre><code>clonefork() {
 hub clone "$1"
 cd "${1##*/}"
 hub fork
}
</code></pre>

In your shell:

<pre><code>$ clonefork user/seed-repo
</code></pre>

By "cloneforking" your seed repo, you also get <a href="https://github.com/blog/39-say-hello-to-the-network-graph-visualizer" rel="nofollow">a network graph</a> showing all repos generated off of it.

blocks|key|2355230|text|我刚刚发布了CLI工具，那就是在现有回购基础上创建新项目，甚至远程创建您自己的Github。https://github.com/theJacobDev/binit|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|2355231|entityMap|0|LINK|mutability|MUTABLE|url|https://github.com/theJacobDev/binit^0|1A|10|0|0^^$0|@$1|2|3|4|5|6|7|L|8|@]|9|@$A|M|B|N|1|O]]|C|$]]|$1|D|3|-4|5|6|7|P|8|@]|9|@]|C|$]]]|E|$F|$5|G|H|I|C|$J|K]]]]

I just published the CLI tool, thats creating new project based on existing repo and even remotely creating your own on Github.
<a href="https://github.com/theJacobDev/binit" rel="nofollow noreferrer">https://github.com/theJacobDev/binit</a>

blocks|key|244668|text|根据@VonC的指示，我为我的终端创建了一个函数，并将其粘贴到我的别名中。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|244669|每次启动一个新项目时，我都会在GitHub上创建一个回购程序，获取确切的项目名称，然后在终端“bp+newProject”上输入|244670|bp+()+{
#+Clone+the+boilerplate+project+from+GitHub
git+clone+https://github.com/username/boilerplate.git;

#+Rename+the+boilerplate+folder+to+newProject
mv+boilerplate+"$@";

#+Access+the+newProject+folder
cd+"$@";

#+Delet+the+.git+folder
rm+-rf+.git;

#+Initialize+git
git+init;

#+Add;
git+add+.;

#+Commit+using+'initial+setup;+as++message;
git+commit+-m+'initial+setup';

#+And+push+it+
git+remote+add+origin+https://github.com/username/"$@".git;
git+push+-u+origin+master
}|code-block|syntax|javascript|244671|entityMap^0|0|0|0^^$0|@$1|2|3|4|5|6|7|K|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|L|8|@]|9|@]|A|$]]|$1|D|3|E|5|F|7|M|8|@]|9|@]|A|$G|H]]|$1|I|3|-4|5|6|7|N|8|@]|9|@]|A|$]]]|J|$]]

Following @VonC's indications, I created a function for my terminal and pasted it in my alias.

Every time I start a new project, I create a repo on GitHub, grab the exact project name and then just type on my terminal 'bp newProject'

<pre><code>bp () {
# Clone the boilerplate project from GitHub
git clone https://github.com/username/boilerplate.git;

# Rename the boilerplate folder to newProject
mv boilerplate "$@";

# Access the newProject folder
cd "$@";

# Delet the .git folder
rm -rf .git;

# Initialize git
git init;

# Add;
git add .;

# Commit using 'initial setup; as message;
git commit -m 'initial setup';

# And push it 
git remote add origin https://github.com/username/"$@".git;
git push -u origin master
}
</code></pre>

blocks|key|244729|text|这并不是你所要求的，但它也可能有助于解决类似的问题。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|244730|有一个工具可以从yaml配置文件https://github.com/g4s8/gitstrap引导Github存储库。|offset|length|style|CODE|244731|它可以：|244732|在Github上创建新的存储库|ordered-list-item|244733|与本地目录同步|244734|应用模板(如带有徽章、CI信任、许可证等的自述文件)|244735|为Github回购配置webhooks|244736|邀请合作者|244737|因此，您可以为类似的项目编写模板，而不是创建样板回购，并在使用该工具创建新的Github时使用配置文件应用它们。|244738|entityMap|0|LINK|mutability|MUTABLE|url|https://github.com/g4s8/gitstrap^0|0|8|4|G|W|0|0|0|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|14|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|15|8|@$D|16|E|17|F|G]]|9|@$D|18|E|19|1|1A]]|A|$]]|$1|H|3|I|5|6|7|1B|8|@]|9|@]|A|$]]|$1|J|3|K|5|L|7|1C|8|@]|9|@]|A|$]]|$1|M|3|N|5|L|7|1D|8|@]|9|@]|A|$]]|$1|O|3|P|5|L|7|1E|8|@]|9|@]|A|$]]|$1|Q|3|R|5|L|7|1F|8|@]|9|@]|A|$]]|$1|S|3|T|5|L|7|1G|8|@]|9|@]|A|$]]|$1|U|3|V|5|6|7|1H|8|@]|9|@]|A|$]]|$1|W|3|-4|5|6|7|1I|8|@]|9|@]|A|$]]]|X|$Y|$5|Z|10|11|A|$12|13]]]]

It's not exactly what you're asking, but it may also be helpful to solve similar issues.

There is a tool to bootstrap Github repository from <code>yaml</code> config file <a href="https://github.com/g4s8/gitstrap" rel="nofollow noreferrer">https://github.com/g4s8/gitstrap</a>

It can:

<ol>
<li>Create new repository on Github</li>
<li>Sync with local directory</li>
<li>Apply templates (such as README with badges, CI configs, LICENSE stuff, etc)</li>
<li>Configure webhooks for Github repo</li>
<li>Invite collaborators</li>
</ol>

so you can write templates for similar projects instead of creating boilerplate repo,
and apply them using configuration file when creating new Github repo with that tool.

blocks|key|244811|text|我也创造了一个解决这类问题的工具。我使用形成了一个概念和独裁者来指示文件系统的某些部分。|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|244812|独裁者被配置为模板/样板-project。如本例所示：https://github.com/tomasbjerre/dictator-react-boilerplate|244813|独裁者配置可命令性，例如：|244814|{
++"message":+"Copy+react-boilerplate",
++"actions":+[
++++{
++++++"beSupersetOfJsonFile":+"react-boilerplate/package.json",
++++++"target":+"package.json"
++++},
++++{
++++++"copyFrom":+"react-boilerplate",
++++++"target":+"."
++++},
++++{
++++++"haveLineContaining":+["*.tgz"],
++++++"target":+".gitignore"
++++}
++]
}|code-block|syntax|javascript|244815|此独裁者可以作为命令行工具运行：|244816|npx+dictator-react-boilerplate|244817|或者让它与构建工具一起运行，比如：|244818|{
++"name":+"react-boilerplate-example",
++"version":+"1.2.3",
++"description":+"asdasasd",
++"scripts":+{
++++"prepare":+"dictator-react-boilerplate"
++},
++"devDependencies":+{
++++"dictator-react-boilerplate":+"0.0.8"
++}
}|244819|entityMap|0|LINK|mutability|MUTABLE|url|https://github.com/tomasbjerre/dictator-builder|1|2|https://github.com/tomasbjerre/dictator-react-boilerplate^0|K|7|0|S|3|1|0|R|1L|2|0|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|15|8|@]|9|@$A|16|B|17|1|18]|$A|19|B|1A|1|1B]]|C|$]]|$1|D|3|E|5|6|7|1C|8|@]|9|@$A|1D|B|1E|1|1F]]|C|$]]|$1|F|3|G|5|6|7|1G|8|@]|9|@]|C|$]]|$1|H|3|I|5|J|7|1H|8|@]|9|@]|C|$K|L]]|$1|M|3|N|5|6|7|1I|8|@]|9|@]|C|$]]|$1|O|3|P|5|J|7|1J|8|@]|9|@]|C|$K|L]]|$1|Q|3|R|5|6|7|1K|8|@]|9|@]|C|$]]|$1|S|3|T|5|J|7|1L|8|@]|9|@]|C|$K|L]]|$1|U|3|-4|5|6|7|1M|8|@]|9|@]|C|$]]]|V|$W|$5|X|Y|Z|C|$10|11]]|12|$5|X|Y|Z|C|$10|11]]|13|$5|X|Y|Z|C|$10|14]]]]

I, also, created a tool to solve this kind of problem. I <a href="https://github.com/tomasbjerre/dictator-builder" rel="nofollow noreferrer">developed a concept</a> with <a href="https://github.com/tomasbjerre/dictator-builder" rel="nofollow noreferrer">dictators</a> that dictates parts of the filesystem.
A dictator is configured with the template/boilerplate -project. Like this example:
<a href="https://github.com/tomasbjerre/dictator-react-boilerplate" rel="nofollow noreferrer">https://github.com/tomasbjerre/dictator-react-boilerplate</a>
The dictator configures dictatables, like:
<pre><code>{
 &quot;message&quot;: &quot;Copy react-boilerplate&quot;,
 &quot;actions&quot;: [
 {
 &quot;beSupersetOfJsonFile&quot;: &quot;react-boilerplate/package.json&quot;,
 &quot;target&quot;: &quot;package.json&quot;
 },
 {
 &quot;copyFrom&quot;: &quot;react-boilerplate&quot;,
 &quot;target&quot;: &quot;.&quot;
 },
 {
 &quot;haveLineContaining&quot;: [&quot;*.tgz&quot;],
 &quot;target&quot;: &quot;.gitignore&quot;
 }
 ]
}
</code></pre>
This dictator can be run as a command line tool:
<pre><code>npx dictator-react-boilerplate
</code></pre>
Or have it run with your build tool, perhaps like:
<pre><code>{
 &quot;name&quot;: &quot;react-boilerplate-example&quot;,
 &quot;version&quot;: &quot;1.2.3&quot;,
 &quot;description&quot;: &quot;asdasasd&quot;,
 &quot;scripts&quot;: {
 &quot;prepare&quot;: &quot;dictator-react-boilerplate&quot;
 },
 &quot;devDependencies&quot;: {
 &quot;dictator-react-boilerplate&quot;: &quot;0.0.8&quot;
 }
}
</code></pre>

I've created a Laravel "boilerplate" project which contains my commonly used features/libraries.

What's the correct git process for utilising this boilerplate as a basis for new projects? I can think of two options:

<ol>
<li>Fork <code>boilerplate</code> to <code>newproject</code> and begin. I don't have any intention of pulling <code>newproject</code> changes back into <code>boilerplate</code>.</li>
<li>Clone <code>boilerplate</code> and update the remote origin to a new clean repo.</li>
</ol>

I'm leaning towards the 2nd option, as it feels like a nice clean split from the boilerplate code. Will I be losing any cool git possibilities by doing this?

Creating new projects from an existing "boilerplate" repo

翻译质量差，导致语言生硬或混乱。

没有提供实际的解决方法或示例。

解答不清晰，无法理解或解决问题。

页面排版不美观，阅读体验差。

文章

问答

视频

学习中心

腾讯云实验室

直播

竞赛

腾讯云代码分析专区

腾讯iOA零信任安全管理系统专区

腾讯云架构师技术同盟交流圈

腾讯云数据库专区

腾讯云顾问专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯轻量云游戏服专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋

腾讯云代码助手

云原生构建

TAPD 敏捷项目管理

Cloud Studio

SDK中心

API中心

命令行工具

涵盖代码开发、场景应用、自动测试全流程，助你从零构建专属AI助手

一站式MCP教程库，解锁AI应用新玩法

我创建了一个Laravel“样板”项目，其中包含了我常用的特性/库。使用这个样板作为新项目的基础，正确的git过程是什么？我可以想到两种选择：将boilerplate分叉到newproject并开始。我没有任何打算将newproject更改拉回boilerplate。克隆boilerplate并将远程源更新为新的干净回...

问从现有的“样板”回购中创建新项目
EN

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问从现有的“样板”回购中创建新项目EN