Skip to content

Latest commit

 

History

History
53 lines (38 loc) · 2.75 KB

git_dubiousownership.md

File metadata and controls

53 lines (38 loc) · 2.75 KB

IBM i developer getting dubious ownership error when non-owner repo user tries to commit changes

Whether using the iForGit SRCTOGIT command or just using the git command from QShell, PASE or SSH, the following error occurs for any user who doesn't own the git repository.

Example of error in IBM i job log or git command line:

fatal: detected dubious ownership in repository at '/gitrepos/gittest123'.
To add an exception for this directory, call:.                            
.                                                                         
git config --global --add safe.directory /gitrepos/gittest123.

Cause

Looks like this error just started occurring as of git version 2.35.2 Git is being more strict on dir ownerships of local repos.

As of 1/8/2024, the newest available version of git on IBM i is 2.39.3 which means this error can start to occur.

Here’s a sample link to read about it:
https://stackoverflow.com/questions/73485958/how-to-correct-git-reporting-detected-dubious-ownership-in-repository-withou

Resolution

In the last line of the article it shows the following git config change which is probably the appropriate resolution.

Run the following command from each users SSH session or via STRQSH one time only.
git config --global safe.directory '*'

Or have each developer run the following CL command:
IFORGIT/GITQSH CMDLINE('git config --global --add safe.directory ''*''') DSPSTDOUT(*NO)

After running this once for each IBM i git user they should no longer see this issue.

When I tested, this seemed to solve it from my test environment with V7R4.

If you like to manually set you git configuration settings, you can also add the appropriate directive to the .gitconfig file in each user's home directory by editing the file from an SSH shell or with EDTF on IBM i.

.gitconfig sample contents for an IBM i user with safe.directory value set:

[user]
        name = First Last
        email = first.last@domain.com
[core]
        preloadIndex = false
[safe]
        directory = *

If developer happens to call the above command too many times, multiple entries can get added ot the safe.directory setting. This isn't a functional issue, but if desired you can remove all the safe.directory settings for a users .gitconfig file using the following shell command if you want to reset the setting. Or simply edit your .gitconfig file as needed:

Run the following command from each users SSH session or via STRQSH one time only to reset the safe.directory settings.
git config --global --unset-all safe.directory

Or have each developer run the following CL command:
IFORGIT/GITQSH CMDLINE('git config --global --unset-all safe.directory') DSPSTDOUT(*NO)