-
Notifications
You must be signed in to change notification settings - Fork 900
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
manageiq log folder and dirty git #18639
Comments
I'm guessing that you did a Yeah it looks like we don't have a |
@sckhg1367 did you put a PR in? |
We intentionally don't have the .keep file. If I recall it's because on the appliance we replace the log directory with a mount point, to allow bigger disks. If the .keep file is there, then the git instance on the appliance is in an always-dirty state. |
See #17663 |
Reopening @agrare |
It seems that the rationale for having a clean git history was broken by ManageIQ/manageiq-appliance-build@3fb3528#diff-59d2b58eb2d092c0658886c3db5af71dR17 , and we should just fix the clean git history on the appliance cc @kbrock |
@Fryguy Git does not track directories, it only tracks files. So if there are not files under Why would a symbolic link cause a stale git state? |
@kbrock because a symlink is a file |
@agrare ok, so git knows the file is there, but it is not tracking it. so you can stash pop, checkout a different branch and you don't have to deal with a deleted file Maybe add EDIT: ignore this, I looked at the PR. I'm good now |
No description provided.
The text was updated successfully, but these errors were encountered: