Bug 11097

Summary:	Create persistent dummy git user
Product:	[Yocto Project Subprojects] CROPS	Reporter:	Juro Bystricky <juro.bystricky>
Component:	crops-default	Assignee:	Unassigned <unassigned>
Status:	NEW ---	QA Contact:
Severity:	enhancement
Priority:	Medium	CC:	amber.n.elliot, randy.e.witt, randy.macleod, richard.purdie, sgw, tim.orling
Version:	3.1
Target Milestone:	Future
Hardware:	x86
OS:	Multiple
Whiteboard:
OS type for building Yocto:	---	Type of Regression:	---
Verified:		Documentation change:	Don't know
Bug Depends on:	11385
Bug Blocks:

Description Juro Bystricky 2017-02-23 05:19:23 UTC

When building bitbake images in containers one cannot do

   $ git stash

without always being prompted to set git user name and user email.
The values, once entered, are not persistent in the container
so this gets very annoying after a short while.
One solution would be to create some persistent dummy git settings
for user "Johny Container" or something like that.

Comment 1 brian avery 2017-12-08 22:05:33 UTC

Moving to Joshua.

Making a dummy git user is not the best way to solve this.

Either:
1) run git commands in the workdir from the host side where you gitconfig is in ~/.gitconfig
-or-
2) run docker as :
docker run -it --env GIT_CONFIG=/myCONFIG -v ~/.gitconfig:/myCONFIG:ro -v `pwd`:`pwd` crops/poky --workdir=`pwd` 

Which gives you:
pokyuser@ff47ab906591:/home/bavery/src/myBugs$ git config --list  
user.email=brian.avery@intel.com    
user.name=brian avery 
** inside the container **
....

This usage probably just needs to be documented then the big could be closed ...

Comment 2 Randy MacLeod 2023-10-30 15:37:26 UTC

Build move to 5.0 -- ../Randy

Comment 3 Randy MacLeod 2024-04-25 01:13:57 UTC

Bulk move of 5.0 medium importance issues to 5.99.
Move to 5.1 if you want to actively work on an issue.

Comment 4 Randy MacLeod 2024-04-25 01:23:12 UTC

Move to 5.99 since no one is actively working on this issue.
Move to 5.x if you start on a task, please.

Comment 5 Tim Orling 2026-06-25 15:20:46 UTC

Ideas here are probably still valid for future design considerations. Moving to future.