# WIP

## 나중에 읽어보기

<details>

<summary>git</summary>

* 코드베이스 관리
  * [매일 배포하는 팀이 되는 여정(1) — 브랜치 전략 개선하기](https://medium.com/daangn/%EB%A7%A4%EC%9D%BC-%EB%B0%B0%ED%8F%AC%ED%95%98%EB%8A%94-%ED%8C%80%EC%9D%B4-%EB%90%98%EB%8A%94-%EC%97%AC%EC%A0%95-1-%EB%B8%8C%EB%9E%9C%EC%B9%98-%EC%A0%84%EB%9E%B5-%EA%B0%9C%EC%84%A0%ED%95%98%EA%B8%B0-1a1df85b2cff)
  * [매일 배포하는 팀이 되는 여정(2) — Feature Toggle 활용하기](https://medium.com/daangn/%EB%A7%A4%EC%9D%BC-%EB%B0%B0%ED%8F%AC%ED%95%98%EB%8A%94-%ED%8C%80%EC%9D%B4-%EB%90%98%EB%8A%94-%EC%97%AC%EC%A0%95-2-feature-toggle-%ED%99%9C%EC%9A%A9%ED%95%98%EA%B8%B0-b52c4a1810cd)
  * [Git branch 전략(Git-Flow, Github-Flow, Gitlab-Flow)](https://velog.io/@kw2577/Git-branch-%EC%A0%84%EB%9E%B5)
  * [Git Branch 전략 비교 - Git Flow vs GitHub Flow](https://devocean.sk.com/blog/techBoardDetail.do?ID=165571\&boardType=techBlog#:~:text=Git%20Flow%EB%8A%94%20%EC%A0%9C%ED%92%88%20%EC%B6%9C%EC%8B%9C,%EB%B9%A0%EB%A5%B8%20%EC%88%98%EC%A0%95%20%EB%B0%B0%ED%8F%AC%EB%A5%BC%20%EA%B0%80%EB%8A%A5)

* git merge, rebase
  * [\[Git\] Git Merge 란? / 쉽게 이해하기 / Fast Forward / 3-way-merge](https://tlatmsrud.tistory.com/155)
  * [잘 쓰면 아주 좋은 git-rebase onto 옵션](https://driip.me/3e206178-8e6c-4519-be35-55b5afeab30b)
  * #### [Git Rebase 제대로 알고 쓰기 (feat. cherry-pick)](https://readystory.tistory.com/151)
  * #### [Git Merge와 Rebase의 차이, 아름다운고 깔끔한 Git History 만들기.](https://firework-ham.tistory.com/12)
  * #### [Git 브랜치 합치기 : Merge, Rebase, Rebase의 활용 및 위험성](https://nemomemo.tistory.com/99)
  * #### [git branch 잘 이용하기 | 2. 깔끔한 커밋 관리를 위한 rebase](https://coldpresso.tistory.com/39)
  * #### [\[Git 깃\] git rebase 위험성](https://zoosso.tistory.com/1168)
  * #### [\[Git\] merge말고 rebase를 사용해야하는 이유, Rebase vs Merge](https://pearlluck.tistory.com/754)

* git 기타
  * [Git Orphan Branch 생성](https://velog.io/@yjok/Git-Orphan-Branch-%EC%83%9D%EC%84%B1)

</details>

<details>

<summary>spring</summary>

* spring config
  * [Spring 외부 설정 파일 import 및 프로퍼티 리팩터링](https://creampuffy.tistory.com/214)

</details>


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://programmer-jjy.gitbook.io/second-brain/today-i-learned/wip.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.