Skip to content

Commit 937eb05

Browse files
committed
Type: docs/Update readme and add code_of_conduct
Body: 기존에 프로젝트에 대한 설명이 없어서, 프로젝트의 의도와 기능에 대해 간략히 설명하는 단락을 추가했음. 또한 code_of_coduct 파일 추가
1 parent b667023 commit 937eb05

2 files changed

Lines changed: 153 additions & 45 deletions

File tree

CODE_OF_CONDUCT.md

Lines changed: 73 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,73 @@
1+
# Contributor Covenant Code of Conduct
2+
3+
## Our Pledge
4+
5+
In the interest of fostering an open and welcoming environment, we as
6+
contributors and maintainers pledge to making participation in our project and
7+
our community a harassment-free experience for everyone, regardless of age, body
8+
size, disability, ethnicity, gender identity and expression, level of experience,
9+
education, socio-economic status, nationality, personal appearance, race,
10+
religion, or sexual identity and orientation.
11+
12+
## Our Standards
13+
14+
Examples of behavior that contributes to creating a positive environment
15+
include:
16+
17+
- Using welcoming and inclusive language
18+
- Being respectful of differing viewpoints and experiences
19+
- Gracefully accepting constructive criticism
20+
- Focusing on what is best for the community
21+
- Showing empathy towards other community members
22+
23+
Examples of unacceptable behavior by participants include:
24+
25+
- The use of sexualized language or imagery and unwelcome sexual attention or
26+
advances
27+
- Trolling, insulting/derogatory comments, and personal or political attacks
28+
- Public or private harassment
29+
- Publishing others' private information, such as a physical or electronic
30+
address, without explicit permission
31+
- Other conduct which could reasonably be considered inappropriate in a
32+
professional setting
33+
34+
## Our Responsibilities
35+
36+
Project maintainers are responsible for clarifying the standards of acceptable
37+
behavior and are expected to take appropriate and fair corrective action in
38+
response to any instances of unacceptable behavior.
39+
40+
Project maintainers have the right and responsibility to remove, edit, or
41+
reject comments, commits, code, wiki edits, issues, and other contributions
42+
that are not aligned to this Code of Conduct, or to ban temporarily or
43+
permanently any contributor for other behaviors that they deem inappropriate,
44+
threatening, offensive, or harmful.
45+
46+
## Scope
47+
48+
This Code of Conduct applies both within project spaces and in public spaces
49+
when an individual is representing the project or its community. Examples of
50+
representing a project or community include using an official project e-mail
51+
address, posting via an official social media account, or acting as an appointed
52+
representative at an online or offline event. Representation of a project may be
53+
further defined and clarified by project maintainers.
54+
55+
## Enforcement
56+
57+
Instances of abusive, harassing, or otherwise unacceptable behavior may be
58+
reported by contacting the project team at {{ email }}. All
59+
complaints will be reviewed and investigated and will result in a response that
60+
is deemed necessary and appropriate to the circumstances. The project team is
61+
obligated to maintain confidentiality with regard to the reporter of an incident.
62+
Further details of specific enforcement policies may be posted separately.
63+
64+
Project maintainers who do not follow or enforce the Code of Conduct in good
65+
faith may face temporary or permanent repercussions as determined by other
66+
members of the project's leadership.
67+
68+
## Attribution
69+
70+
This Code of Conduct is adapted from the [Contributor Covenant][homepage], version 1.4,
71+
available at https://www.contributor-covenant.org/version/1/4/code-of-conduct.html
72+
73+
[homepage]: https://www.contributor-covenant.org

README.md

Lines changed: 80 additions & 45 deletions
Original file line numberDiff line numberDiff line change
@@ -4,19 +4,39 @@
44
<p style="font-weight: 700; font-size: 30px;">Make Your Git Easier</p>
55
</div></div>
66

7+
Pretty Git is browser-based git GUI program which supports basic browsing functionalities and several git-related commands.
8+
Git is a powerful version control system and it is easy to use once you get used to various git commands and its workflow. But For Beginners, it is true that git can be complex to use and it really takes time to apply git workflow to your project at the first time.
9+
Our team also stucked at this stage when we were beginner git and then started this project to make git usage more easier.
10+
It's always good starting point to understand git workflow with comprehensive GUI supports.
11+
we are sure that you will be familiar with git workflow while you using our project.
12+
13+
We are always open to get any feedbacks and anyone who wants to contribute this project.
14+
715
# Tested environment
816

9-
- machine: MacOS Ventura 13.3.1, Windows OS 11
10-
- runtime : node v19.8.1
11-
- libraries
12-
- axios : v1.4.0
13-
- express : v4.18.2
14-
- pug : v3.0.2
15-
- nodemon : v2.0.20
16-
- simple-git: v3.18.0
17-
- minimatch: v9.0.0
17+
| machine | version |
18+
| ---------- | -------------- |
19+
| MacOS | Ventura 13.3.1 |
20+
| Windows OS | 11 |
21+
22+
| Runtime | version |
23+
| ------- | ------- |
24+
| node.js | v19.8.1 |
25+
26+
| libraries | version |
27+
| ---------- | -------- |
28+
| axios | v1.4.0 |
29+
| express | v4.18.2 |
30+
| pug | v3.0.2 |
31+
| nodemon | v2.0.20 |
32+
| simple-git | v.3.18.0 |
33+
| minimatch | v9.0.0 |
1834

19-
# Prerequisites
35+
# Installation
36+
37+
## 1. prerequisites
38+
39+
### Git config
2040

2141
- If you don't have a git, Install git first and then config your git account
2242

@@ -27,6 +47,8 @@
2747
git config --global user.name "your name"
2848
```
2949
50+
### Node.js
51+
3052
- Install node.js runtime corresponding your machine platform. We highly recommend you to install LTS version.
3153
- [official node.js site](https://nodejs.org/ko)
3254
- To run local server in your machine, you need to install 'nodemon' package globally. Follow below command.
@@ -45,16 +67,12 @@
4567
npm i -g nodemon
4668
```
4769
48-
- Install 'simple-git' npm module.
49-
50-
```
51-
npm i simple-git
52-
```
70+
### Chrome browser
5371
5472
- Our project doesn't guarantee that it will work on every browser. We recommend you to use chrome browser.
5573
- [chrome browser download](https://www.google.com/chrome/?brand=CHBD&brand=CHBD&gclid=Cj0KCQjwmN2iBhCrARIsAG_G2i6teiD4fIvR-a5CQEAxNGkxlercrsgwv6onbD1pMKGr1soGa1exmQEaAm6bEALw_wcB&gclsrc=aw.ds)
5674
57-
# How to run
75+
## 2. Download source codes and Install Dependencies
5876
5977
1. Clone our repo or Download source files.
6078
```
@@ -64,23 +82,39 @@
6482
```
6583
npm install
6684
```
67-
3. Run the file server by typing below command and Enjoy it!
6885
69-
```
86+
# How to run
87+
88+
1. First, To run the pretty-git local server, move to the directory path where you clone our project source code.
89+
<br>
90+
Then, you can run the server by running below command
91+
92+
```bash
7093
npm run dev
7194
```
7295

73-
<span style="color: orangered;">[Warning]</span> If you already running something on same port, you will see below error.
96+
If the sever successfully running, you can see this lines in your terminal screen
97+
98+
```bash
99+
[nodemon] 2.0.20
100+
[nodemon] to restart at any time, enter rs
101+
[nodemon] watching path(s): *.*
102+
[nodemon] watching extensions: js,mjs,json
103+
[nodemon] starting node src/index.js
104+
Server running on port 3000
105+
```
106+
107+
2. <span style="color: orangered;">[Warning]</span> If you already running something on same port, you will see below error.
74108

75109
```
76110
Emitted 'error' event on Server instance at:
77-
at emitErrorNT (node:net:1801:8)
78-
at process.processTicksAndRejections (node:internal/process/task_queues:82:21) {
79-
code: 'EADDRINUSE',
80-
errno: -48,
81-
syscall: 'listen',
82-
address: '::',
83-
port: 3000
111+
at emitErrorNT (node:net:1801:8)
112+
at process.processTicksAndRejections (node:internal/process/task_queues:82:21) {
113+
code: 'EADDRINUSE',
114+
errno: -48,
115+
syscall: 'listen',
116+
address: '::',
117+
port: 3000
84118
}
85119
86120
Node.js v19.8.1
@@ -91,8 +125,8 @@
91125
a. Kill the port you use and re-run the sever.
92126
b. Go to src directory('~/pretty-git/src') and modify the `PORT` value inside index.js
93127

94-
```
95-
const PORT = 3000; //<-- modify the number here.
128+
```javascript
129+
const PORT = 3000; //<-- modify the port number here.
96130
```
97131

98132
# New Features in v2.0.0
@@ -143,19 +177,19 @@ Now, you can mangage your branches on the browser.
143177

144178
- When you click the 'Git Log' button to the left of the 'Git Status' button, Pretty-git will show you the commit history of your project in the form of a graph.
145179

146-
- Click 'Git Log' button.
147-
<div align="center">
148-
<div style="display:flex; justify-content: center;"><img width ="300px" height="px" src="src/public/readmeimg/log-btn.png" alt="current branch menu"/></div></div><br>
180+
- Click 'Git Log' button.
181+
<div align="center">
182+
<div style="display:flex; justify-content: center;"><img width ="300px" height="px" src="src/public/readmeimg/log-btn.png" alt="current branch menu"/></div></div><br>
149183

150-
- Pretty-git will show you the graph. The graph includes the workflow of the current branch.
151-
<div align="center">
152-
<div style="display:flex; justify-content: center;"><img width ="500px" src="src/public/readmeimg/commit-history.png" alt="current branch menu"/></div></div><br>
184+
- Pretty-git will show you the graph. The graph includes the workflow of the current branch.
185+
<div align="center">
186+
<div style="display:flex; justify-content: center;"><img width ="500px" src="src/public/readmeimg/commit-history.png" alt="current branch menu"/></div></div><br>
153187

154-
- Furthermore, If you choose a commit object shaped yellow circle, Pretty-git will provide the detailed information about the commit.
155-
<div align="center">
156-
<div style="display:flex; justify-content: center;"><img width ="500px" src="src/public/readmeimg/detail-commit.png" alt="current branch menu"/></div></div><br>
188+
- Furthermore, If you choose a commit object shaped yellow circle, Pretty-git will provide the detailed information about the commit.
189+
<div align="center">
190+
<div style="display:flex; justify-content: center;"><img width ="500px" src="src/public/readmeimg/detail-commit.png" alt="current branch menu"/></div></div><br>
157191

158-
- If you want to close the detailed commit tab, just click the 'close' button.
192+
- If you want to close the detailed commit tab, just click the 'close' button.
159193

160194
## 4. Git clone from GitHub
161195

@@ -172,12 +206,12 @@ You can easily clone both private and public repository using HTTPS of it.
172206
<div style="display:flex; justify-content: center;"><img width ="400px" src="src/public/readmeimg/public-repo.png" alt="current branch menu"/></div></div><br>
173207

174208
- If you click the 'private repo', It will ask you the address of the repository.
175-
<div align="center">
176-
<div style="display:flex; justify-content: center;"><img width ="400px" src="src/public/readmeimg/private-url.png" alt="current branch menu"/></div></div><br>
209+
<div align="center">
210+
<div style="display:flex; justify-content: center;"><img width ="400px" src="src/public/readmeimg/private-url.png" alt="current branch menu"/></div></div><br>
177211

178-
- If you already have the id and token that needed for cloning, Pretty-git directly clone the private repository.
212+
- If you already have the id and token that needed for cloning, Pretty-git directly clone the private repository.
179213

180-
- Otherwise, if you have no information that needed for cloning, Pretty-git ask you the id, token about the repository.
214+
- Otherwise, if you have no information that needed for cloning, Pretty-git ask you the id, token about the repository.
181215

182216
<div align="center">
183217
<div style="display:flex; justify-content: center;"><img width ="400px" src="src/public/readmeimg/enter-id.png" alt="current branch menu"/></div></div><br>
@@ -194,9 +228,10 @@ You can easily clone both private and public repository using HTTPS of it.
194228
- If you think an information of the access token is wrong or want to renew the token information by yourselves, you can update it in .gitconfig, which is global config file of git VCS.
195229

196230
- To enter and edit .gitconfig file, run the below command (The command might not work depending on your machine, especially Windows)
197-
```bash
198-
vim ~/.gitconfig
199-
```
231+
232+
```bash
233+
vim ~/.gitconfig
234+
```
200235

201236
<div align="center">
202237
<div style="display:flex; justify-content: center;"><img width ="400px" src="src/public/readmeimg/config.png" alt="current branch menu"/></div></div><br>

0 commit comments

Comments
 (0)