Skip to content
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

Leverage CLI to automatically create missing .gitconfig file #267

Closed
borland667 opened this issue May 14, 2024 · 1 comment
Closed

Leverage CLI to automatically create missing .gitconfig file #267

borland667 opened this issue May 14, 2024 · 1 comment
Assignees
Labels
bug Something isn't working patch

Comments

@borland667
Copy link
Contributor

Describe the Bug

The Leverage CLI does not automatically create a .gitconfig file in the user's home directory if it is missing, leading to errors during execution.

Expected Behavior

The Leverage CLI should check for the existence of the .gitconfig file in the user's home directory (~/.gitconfig) and create it if it does not exist, ensuring smooth execution without manual intervention.

Steps to Reproduce

Steps to reproduce the behavior:

  1. Go to a system where the .gitconfig file does not exist in the home directory.
  2. Run any Leverage CLI command that requires the .gitconfig file, e.g., leverage tf shell.
  3. Observe the error related to the missing .gitconfig file.

Screenshots

If applicable, add screenshots or logs to help explain your problem.

Environment (please complete the following information):

  • OS: Linux, OSX
  • Leverage CLI Version: 1.12.1
  • Docker Version: 26.1.1
  • Python Version: 3.11.6

Additional Context

This issue is a known problem that affects users when the .gitconfig file is missing. The proposed solution is to update the CLI to automatically create the .gitconfig file in the user's home directory (~/.gitconfig) if it is not found. This enhancement will improve the user experience by reducing manual setup steps.

@borland667 borland667 added bug Something isn't working patch labels May 14, 2024
@borland667 borland667 self-assigned this May 14, 2024
@exequielrafaela exequielrafaela assigned Franr and unassigned borland667 Dec 30, 2024
@Franr
Copy link
Contributor

Franr commented Feb 1, 2025

Fixed in #295

@Franr Franr closed this as completed Feb 1, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working patch
Projects
None yet
Development

No branches or pull requests

2 participants