Skip to content

Commit fe6aa61

Browse files
author
Seungwon An
authored
Merge pull request #2 from seungwonme/pull-request
PR demo
2 parents 9631c17 + 020729d commit fe6aa61

File tree

3 files changed

+90
-1
lines changed

3 files changed

+90
-1
lines changed

.github/CODEOWNERS

Lines changed: 80 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,80 @@
1+
# CODEOWNERS로 코드 리뷰어 지정하기
2+
* @seungwonme
3+
4+
# This is a comment.
5+
# Each line is a file pattern followed by one or more owners.
6+
7+
# These owners will be the default owners for everything in
8+
# the repo. Unless a later match takes precedence,
9+
# @global-owner1 and @global-owner2 will be requested for
10+
# review when someone opens a pull request.
11+
12+
# * @global-owner1 @global-owner2
13+
14+
# Order is important; the last matching pattern takes the most
15+
# precedence. When someone opens a pull request that only
16+
# modifies JS files, only @js-owner and not the global
17+
# owner(s) will be requested for a review.
18+
19+
# *.js @js-owner #This is an inline comment.
20+
21+
# You can also use email addresses if you prefer. They'll be
22+
# used to look up users just like we do for commit author
23+
# emails.
24+
25+
26+
27+
# Teams can be specified as code owners as well. Teams should
28+
# be identified in the format @org/team-name. Teams must have
29+
# explicit write access to the repository. In this example,
30+
# the octocats team in the octo-org organization owns all .txt files.
31+
32+
# *.txt @octo-org/octocats
33+
34+
# In this example, @doctocat owns any files in the build/logs
35+
# directory at the root of the repository and any of its
36+
# subdirectories.
37+
38+
# /build/logs/ @doctocat
39+
40+
# The `docs/*` pattern will match files like
41+
# `docs/getting-started.md` but not further nested files like
42+
# `docs/build-app/troubleshooting.md`.
43+
44+
45+
46+
# In this example, @octocat owns any file in an apps directory
47+
# anywhere in your repository.
48+
49+
# apps/ @octocat
50+
51+
# In this example, @doctocat owns any file in the `/docs`
52+
# directory in the root of your repository and any of its
53+
# subdirectories.
54+
55+
# /docs/ @doctocat
56+
57+
# In this example, any change inside the `/scripts` directory
58+
# will require approval from @doctocat or @octocat.
59+
60+
# /scripts/ @doctocat @octocat
61+
62+
# In this example, @octocat owns any file in a `/logs` directory such as
63+
# `/build/logs`, `/scripts/logs`, and `/deeply/nested/logs`. Any changes
64+
# in a `/logs` directory will require approval from @octocat.
65+
66+
# **/logs @octocat
67+
68+
# In this example, @octocat owns any file in the `/apps`
69+
# directory in the root of your repository except for the `/apps/github`
70+
# subdirectory, as its owners are left empty.
71+
72+
# /apps/ @octocat
73+
# /apps/github
74+
75+
# In this example, @octocat owns any file in the `/apps`
76+
# directory in the root of your repository except for the `/apps/github`
77+
# subdirectory, as this subdirectory has its own owner @doctocat
78+
79+
# /apps/ @octocat
80+
# /apps/github @doctocat

PR.md

Lines changed: 3 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,3 @@
1+
Pull Request를 만들기 위한 파일입니다.
2+
3+
댓글을 달 수 있습니다.

README.md

Lines changed: 7 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -8,12 +8,18 @@
88

99
![](./img/GitWorkflow.png)
1010

11-
## Git Branch Model
11+
## Git Branch
12+
13+
### Git Branch Model
1214
- [{Git,Github,Gitlab} Flow 1](https://ujuc.github.io/2015/12/16/git-flow-github-flow-gitlab-flow/)
1315
- [{Git,Github,Gitlab} Flow 2](https://wiki.yowu.dev/ko/dev/Git/about-git-github-gitlab-flow)
1416
- [Trunk Based Development](https://trunkbaseddevelopment.com)
1517
- [Trunk Based Development 기술 블로그](https://tech.mfort.co.kr/blog/2022-08-05-trunk-based-development/)
1618

19+
### Git Branch Policy
20+
- [Branch Protection Rule](https://docs.github.com/ko/repositories/configuring-branches-and-merges-in-your-repository/managing-protected-branches/managing-a-branch-protection-rule)
21+
- [CODEOWNERS file](https://docs.github.com/ko/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/about-code-owners)
22+
1723
## Git Command
1824

1925
### restore

0 commit comments

Comments
 (0)