Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Show HN: Git-Ready to Deploy? Check for uncommitted and non-pushed changes

github.com

Post reply on HN
Print view View original

1–10 of 26 posts

Re: Show HN: Git-Ready to Deploy? Check for uncommitted and non-pushed changes

#3

Post by Matt3o12_ »

TekMol wrote: post #2

I'm confused. How is that different from 'git status'?

Well, git status doesn’t show unpushed changes from other branches but when I deploy, I normally go into the deployment branch and run git status there. So the unpushed changes in other branches would be quite insignificant.

But everyone’s workflow is different. The author maybe should have added a reason why he uses that instead of git status

Re: Show HN: Git-Ready to Deploy? Check for uncommitted and non-pushed changes

#5

Post by TekMol »

Matt3o12_ wrote: post #3
TekMol wrote: post #2

I'm confused. How is that different from 'git status'?

Well, git status doesn’t show unpushed changes from other branches but when I deploy, I normally go into the deployment branch and run git status there. So the unpushed changes in other branches would be quite insignificant. But everyone’s workflow is different. The author maybe should have added a reason why he uses that instead of git status

Ok, so that would be a difference. Showing all unpushed changes from all branches.

Seems unusual that all branches are involved in deployment though. Isn't the typical workflow that only one branch get's deployed to the user facing machine?

Re: Show HN: Git-Ready to Deploy? Check for uncommitted and non-pushed changes

#6

Post by TekMol »

oleks wrote: post #4
TekMol wrote: post #2

I'm confused. How is that different from 'git status'?

It first performs a git status, then fetches changes from upstream, and checks if all local changes have been pushed upstream (using git cherry).

I'm curious what the workflow is here.

My workflow looks like this:

A feature branch is mature enough to get merged into master. So I merge it into master on the staging server. And then push it to the public server.

Re: Show HN: Git-Ready to Deploy? Check for uncommitted and non-pushed changes

#7

Post by oleks »

TekMol wrote: post #6
oleks wrote: post #4

Earlier quoted context omitted.

It first performs a git status, then fetches changes from upstream, and checks if all local changes have been pushed upstream (using git cherry).

I'm curious what the workflow is here. My workflow looks like this: A feature branch is mature enough to get merged into master. So I merge it into master on the staging server. And then push it to the public server.

Yes, so this is useful where deployment is "manual" in the sense that it is not a mere git push. It is bad practice to have git data lying around among otherwise public files, so you have to either set up git hooks on the public server, or fine-tune your public server access rights. Both require (slightly) more work than simply not pushing the git data in the first place.

Re: Show HN: Git-Ready to Deploy? Check for uncommitted and non-pushed changes

#9

Post by oleks »

wereHamster wrote: post #8

Do you know about `git-sh-setup`? As in: . "$(git --exec-path)/git-sh-setup" require_clean_work_tree "bump" "Please commit or stash them." https://git-scm.com/docs/git-sh-setup

This will only spot uncommitted changes to tracked files. I want a completely clean repository before I deploy, where there are neither uncommitted changes to tracked files, nor (new) untracked files.

But no, I did not know of git-sh-setup, thanks for the tip :-)

Post reply on HN