I always do a git status just to be sure before a commit
this post was submitted on 14 Oct 2023
11 points (86.7% liked)
Programming
17483 readers
191 users here now
Welcome to the main community in programming.dev! Feel free to post anything relating to programming here!
Cross posting is strongly encouraged in the instance. If you feel your post or another person's post makes sense in another community cross post into it.
Hope you enjoy the instance!
Rules
Rules
- Follow the programming.dev instance rules
- Keep content related to programming in some way
- If you're posting long videos try to add in some form of tldr for those who don't want to watch videos
Wormhole
Follow the wormhole through a path of communities [email protected]
founded 1 year ago
MODERATORS
Or use tig. It's a great CLI tool to view git status, stage/unstage, and view history. And I never really hear anyone talk about it.
Thanks, i will take a look
When staging files to commit, you can use an interactive patch:
git add -p
Before you make your commit, you can inspect what's being committed:
git diff --cached
If there are things you want to remove, you can do so with interactive patches, too:
git reset -p
You can also pass directories or files to any of these commands to include a subset of your project in the command.
omg these are great commands, thanks for sharing :)
git is definitely a weak spot for me in general, there's a lot of commands and similar commands, so my approach until now has been to forget they exist haha
You bet! You can always check the man pages by adding a hyphen between the git commands, too, like so:
man git-diff
man git-add
It's exhaustive, but you can search the page with slash (/) π
honestly, i check the manpages for anything else but i never have with git π€£ however I didn't know how to access the man pages for subcommands, thanks!! :)
Even better, just choose exactly which files to add to a commit, and keep the commits small and meaningful units of work! If you never use the shorthand, you won't have this issue, and your commit history will be easier to understand and expand upon!
This is what i should be doing :)
I have been justifying it away though cause it's early stages of the project so it's hard to get my bearings. But the dust is starting to settle enough now that I can probably think about committing units of work rather than this daily snapshotting ive been doing
Can't you ssh into your work computer?
In my 20 year career, Iβve never had a single position where I could ssh into my work machine from a remote location.
I would say that if you have been able to do that, itβs exceptionally rare, and there are a number of security red flags of your organization is allowing that.
Work laptop + VPN should take care of most security stuff, no?
Being able to SSH remotely without VPN would be certain red flag.
Even with VPN, remote connections are frequently partitioned from on-premises machines, either on purpose, or because the network is large enough to require different subnets.
Having VPN definitely makes it possible and far less risky, but itβs still not really a guarantee, and that could still indicate a more relaxed security posture.
No judgement, itβs just not typical in a lot of environments.