* Explanation of removing large files using bfg
* doctoc applied to removing large files guide
* Remove large files: clean up wording
* Add subheadings to the large file removal section in preparation for git-filter-branch explanation
* large file removal: clean up headings
* large file removal: force push considerations note
* Add word "private" to sensitive data section for searchability
* Finish git-filter-branch instructions
* Minor grammatical changes and simplifications.
Like discussed in the PR this commit improves the quested section
regarding lesser spelling mistakes and improved wording. The discussion
about --no-edit lead to no changes required, so it is not altered.
See https://github.com/k88hudson/git-flight-rules/pull/256
I have accidentally staged many files in my working copy, and was looking for a way to unstage them by filename as I had some staged files that I wanted to keep. Didn't see anything that addressed my specific issue on the README, so thought of adding it here.
* 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.
yaame
MarvinJWendt
Alexander Gómez
Richard Littauer
Dustin Freeman
Timo Sand
Maroun Maroun
Tommy Williams
abdel ali
Richard Littauer
nielsonm
Matthias Baumgarten
Cole
Samy Kacimi
cyblue9
hoannc
joseph
Cam Hardy
Jake
Henry Darnell
Dakota Chambers
Matthieu V
Ricardo Lopes
David Glasser
Nicolas Zachow
grantslone
hadongsoo
Daryl