-
Notifications
You must be signed in to change notification settings - Fork 1
/
Copy pathindex.html
110 lines (97 loc) · 3.55 KB
/
index.html
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
<!DOCTYPE html>
<html>
<head>
<meta chrset="utf-8" />
<meta http-equiv="X-UA-Compatible" content="IE=edge">
<meta name="viewport" content="width=device-width, initial-scale=1">
<title>Git Flow Setup</title>
<link href="css/bootstrap.min.css" rel="stylesheet" />
<link href="css/blog.css" rel="stylesheet">
<link href="css/gitflow.css" rel="stylesheet">
</head>
<body>
<div class="blog-masthead">
<div class="container">
<nav class="nav blog-nav">
<a class="nav-link active" href="./">setup</a>
<a class="nav-link" href="with-gitflow.html">with git-flow</a>
<a class="nav-link" href="without-gitflow.html">without git-flow</a>
<a class="nav-link" href="readme.html">readme</a>
<a class="nav-link" href="graphic.html">graphic</a>
</nav>
</div>
</div>
<div class="blog-header">
<div class="container">
<h1 class="blog-title">Git Flow</h1>
<p class="lead blog-description">Using git flow -- or not</p>
</div>
</div>
<div class="container">
<a name="install"></a>
<div class="row">
<h2>Install</h2>
<h5>OSX - Homebrew</h5>
<pre>$ brew install git-flow</pre>
<h5>OSX - Macports</h5>
<pre>$ ports install git-flow</pre>
<h5>Linux</h5>
<pre>$ apt-get install git-flow</pre>
<h5>Windows (Cygwin)</h5>
<pre>$ wget -q -O - --no-check-certificate https://github.com/nvie/gitflow/raw/develop/contrib/gitflow-installer.sh | bash</pre>
<div class="alert alert-info" role="alert">
You need wget and util-linux to install git-flow.
</div>
</div>
<a name="init"></a>
<div class="row">
<h2>Initialize</h2>
<pre>
$ cd my/project
$ git commit -am "Initial commit"
$ git remote add origin [email protected]:username/Project-Name.git
$ git push -u origin main</pre>
</div>
<a name="prepare"></a>
<div class="row">
<h2>Prepare Repository for Development</h2>
<p>Create development branch, push it to the server</p>
<pre>
$ git checkout -b develop
$ git push -u origin develop</pre>
<div class="alert alert-info" role="alert">
Make sure to set the <strong>default branch</strong> to `develop` on github!
</div>
</div>
<a name="setup"></a>
<div class="row">
<h2>Setup Git Flow</h2>
<p>You will be prompted, as seen below, for what branches you'd like to use. You can just hit `enter` for all.</p>
<p><strong>Notes:</strong></p>
<ol>
<li>To use the defaults you can use the `-d` flag</li>
<li>You can set a default version tag prefix if you prefer. eg: `v`</li>
</ol>
<pre>
$ git flow init [-d]
Which branch should be used for bringing forth production releases?
- develop
- main
Branch name for production releases: [main]
Which branch should be used for integration of the "next release"?
- develop
Branch name for "next release" development: [develop]
How to name your supporting branch prefixes?
Feature branches? [feature/]
Release branches? [release/]
Hotfix branches? [hotfix/]
Support branches? [support/]
Version tag prefix? []</pre>
</div>
</div><!-- /.container -->
<footer class="blog-footer">
<p>Using the <a href="http://nvie.com/posts/a-successful-git-branching-model/">Git branching model</a> from <a href="https://twitter.com/nvie">@nvie</a></p>
<p>Built by <a href="https://twitter.com/skoch">@skoch</a></p>
</footer>
</body>
</html>