Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add tip on renaming files tracked with git #9

Merged
merged 2 commits into from
Nov 21, 2024
Merged

Conversation

egrace479
Copy link
Member

Also removes the reference to emacs.

@egrace479 egrace479 requested a review from thompsonmj November 19, 2024 21:50
Copy link
Member Author

@egrace479 egrace479 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'd suggest this smaller change to avoid the git add . seeming like a suggested method. Then I can add another "Pro Tip" at line 46 to the effect:

After using git add <folder> or git add <regex> (a pattern match), run git status to ensure that all intended files--and only intended files--are staged for commit.

docs/wiki-guide/Command-Line-Cheat-Sheet.md Outdated Show resolved Hide resolved
@thompsonmj
Copy link
Contributor

thompsonmj commented Nov 20, 2024

I'd suggest this smaller change ...

That's good, though I often just list the files by name, e.g. git add <path/to/file1> <path/to/file2> <path/to/file3> to scope the commit well. But for brevity, it looks good as is.

Copy link
Contributor

@thompsonmj thompsonmj left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good!

@egrace479 egrace479 merged commit dc5d08c into main Nov 21, 2024
@egrace479 egrace479 deleted the update/cheat-sheet branch November 21, 2024 18:18
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants