git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Git - Pushing to a production website

From
44jxdq6fqee2h@dyweni.com <4jxdq6fqee2h@dyweni.com>
Date
Jan 10, 2009, 04:23 UTC
Message-ID
<20090109222344.3539138a@family.dyweni.com>
Hi,
Our company's website is stored in a GIT Repository.

The repository is coded for our test server. When we push updates to the production server, have manually run a script to patch several files to make the code work on the production server (i.e. port numbers, etc).

I'd like to write a script to email me whenever someone changes files on the production server without checking those changes back into git (i.e. running 'git status | grep "nothing to commit" ...').

However, this approach get confused by the files patched to work correctly.

Is there any way to 'save' those patched files so they don't get reported by 'git status', yet not mung up the git history every time we push out an update?

Thanks!
Next: Boyd Stephen Smith Jr.
Message 1 of 10 in “Git - Pushing to a production website”
  1. 4jxdq6fqee2h@dyweni.comJan 10, 2009
  2. Boyd Stephen Smith Jr.Jan 10, 2009
  3. 4jxdq6fqee2h@dyweni.comJan 10, 2009
  4. Boyd Stephen Smith Jr.Jan 10, 2009
  5. 4jxdq6fqee2h@dyweni.comJan 10, 2009
  6. Boyd Stephen Smith Jr.Jan 10, 2009
  7. david@lang.hmJan 10, 2009
  8. Jacob HelwigJan 10, 2009
  9. David AguilarJan 10, 2009
  10. Sitaram ChamartyJan 10, 2009

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.