Skip to content

Commit 7e5db88

Browse files
committed
Adding release strategy overview to README
1 parent 711e5ca commit 7e5db88

File tree

2 files changed

+16
-15
lines changed

2 files changed

+16
-15
lines changed

.gitignore

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,2 @@
1+
.idea/*
2+

README.md

Lines changed: 14 additions & 15 deletions
Original file line numberDiff line numberDiff line change
@@ -1,15 +1,14 @@
1-
# promote-single
2-
3-
dsfasdfasdfads
4-
adsf
5-
asdfdsaf
6-
adsf
7-
asf
8-
asd
9-
fdas
10-
fdas
11-
adfs
12-
13-
14-
15-
1+
# Single Branch Environment Example #
2+
## Overview ##
3+
Making all pull requests against a single “master” branch is
4+
an excellent strategy to quickly get up and running while
5+
reducing the cognitive overhead for developers and managers.
6+
This ease of use makes a single branch release strategy popular
7+
among open source developers and projects who have simple deployment
8+
needs.
9+
10+
This release strategy centers around a single master branch
11+
where all of the edits from the contributors is staged. Forks,
12+
branches, and direct commits all funnel into this primary branch
13+
and then the maintainers determine when to cut a new release and
14+
push it out to their end-users.

0 commit comments

Comments
 (0)