I use feature branched for everything, usually named after an issue number. I created a script that allows me to commit whenever I get a task done, not the whole feature, and that script takes care of adding the files, committing them with a message, tags it with the issue number (current branch name), and pushes to remote. That way, every time I save, the changes are saved on the remote GIT repo in case my computer dies or something.
Here's the code in case you wanted to use it:
savework()
{
if git diff --exit-code --quiet
then
echo "There are no changes to save, NONE!";
else
echo "Stage everything for commit -------------";
addit; # an alias for "git add -A ."
echo "Commit all changes with message $@ --------------";
commit "$@"; #commit is an alias for "git commit -m"
echo "Push branch to remote --------------"
psh; # an alias for git push origin $(git branch | grep "*" | sed "s/* //")
fi
Faraday Future | Gardena, CA or Redwood City, CA | full-time and internships
Faraday Future is a California mobility company bringing a tech approach to clean transportation. At FF, we believe that by placing equal emphasis on automotive and technology disciplines, our team of experts is uniquely positioned to take a user-centric, technology-first approach to vehicle design with the ultimate aim of connecting the automotive experience with the rest of your life.
A couple positions not listed on our site, which we are also currently hiring for, is Android Developers and Web Developers, if you've been working with MeteorJS and ReactJS, even better.
Here's the code in case you wanted to use it:
savework()
{
}Use it like this: savework "COMMIT MESSAGE HERE"