Re: Recent changes for the unsafe directory handling - TINY improvement requested in error output
- From
Nathan Neulinger <nneul@neulinger.org>
- Date
- Apr 20, 2022, 13:29 UTC
- Message-ID
- <abf42057-7b40-0995-45a8-ac927800c485@neulinger.org>
- In-Reply-To
- <e689bb30-dc7f-6e3d-a8d5-864e00de59d4@gmail.com>
On 4/20/22 01:16, Bagas Sanjaya wrote:
Show 13 quoted lines
> On 4/19/22 18:26, Nathan Neulinger wrote: >> However, if you do a 'git diff' - such as what you might naturally do right before attempting a 'git commit' - you do NOT get any useful response: >> >> root@SERVER:/local/APPNAME/bin# git diff >> warning: Not a git repository. Use --no-index to compare two paths outside a working tree >> usage: git diff --no-index [<options>] <path> <path> >> ...snip-long-diff-help... >> >> Please consider a small improvement to have the git diff help output (if displayed due to the repo exclusion warning) - ALSO display the 'git config' suggestion at the end of the output, instead of me having to remember - oh, go issue status to get the command hint to go set the exclusion. Would also be useful to have the git diff output do the same 'unsafe repository' message about ownership. >> > > I assumed that you have /local/APPNAME/bin shared by users (maybe via > NFS or something else), right?
Actually, each /local/APPUSER is the base of the clone - dev environment on master/main, test env on 'test' and prod env on 'production'.
Depending on the deployment we're either logging in directly as the application, or as common or admin accounts that have access over multiple application directory trees. The applications themselves each have their own userid for permissions isolation.
-- Nathan ------------------------------------------------------------ Nathan Neulinger nneul@neulinger.org Neulinger Consulting (573) 612-1412