* added guide for amending sensitive data that was committed/pushed
* added formatting and more solutions for amending sensitive data
* added a few sentences to explain why any sensitive data should be considered compromised once it's been committed
Ignoring local changes can be really handy for creds/credfile templates, I've found it particularly handy with Discord bot development where the configuration file can have an expected structure and expects you to add tokens to that config file
* Add guide to working with tags and branches that share the same name.
Add the error scene when trying to push a tag/branch that share the same name and the commands to fix that problem.
* Fix formatting of an error statement.
Creators of Sublime Text recently launched a Git client, it has a lot of potential !
I think it has its place in this list 😃
Please tell me if my phrasing is wrong
Previously, this document the same command for "I wrote the wrong thing in a commit message" and "I need to add staged changes to the previous commit". These are different operations! Now, the former has a command that only changes the commit message (without adding staged changes), and the latter has commands to add staged changes with or without updating the commit message.
I also added "reword" and "extend" aliases to the sample gitconfig for using the two pieces of `git commit --amend` separately.
* make a readme
make a new readme for Korean
* git-flight-rule 번역 중간과정 01
브랜치 부분에서 한번 커밋
* git-flight-rule 번역 중간과정 02
머지 시작
* git-flight-rule 번역 1차 종료후 점검
* 점검 후 첫 완료
* 오타 수정 몇가지 수정
* 네비게이션 링크 추가
* 표현 수정
When viewing the git-flight-rules repository under gitlab, it lists the first README*.md file, which for some reason it sorts `-` before `.`. This changes the Spanish README's filename to match the other two translations already in this repository.
* Add missing HEAD argument in 2 Git commands
These commands had been inserted in #148 and (over)simplified in #163.
The issue is that `git push <remote>` and `git push -u <remote>` will
typically raise the error below (unlike `git push <remote> HEAD`):
--8<---------------cut here---------------start------------->8---
fatal: The current branch new-branch has no upstream branch.
To push the current branch and set the remote as upstream, use
git push --set-upstream origin new-branch
--8<---------------cut here---------------end--------------->8---
* Add doc URL & Avoid triple backquotes
Runs doctoc for README*.md.
If in newly doctoc'ed README*.md there are any diffs against
ones commited in git HEAD then the test failes.
The script are using the latest anchor-markdown-header from repo
to avoid the bug with non-ASCII headers.
