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

Only git reset operation after a git clone #1176

Merged
merged 2 commits into from
Feb 24, 2023
Merged

Conversation

olblak
Copy link
Member

@olblak olblak commented Feb 24, 2023

Fix #1133

Only execute git reset operation after a git clone and not anymore after each git checkout operation

Test

To test this pull request, you can run the following commands:

cp <to_package_directory>
go test

Additional Information

Tradeoff

I hesitated to totally remove the git reset operation but decided to keep at the beginning of a pipeline run as an intermediary step.
This reduce the risk of working from a "none" clean directory and we can still disable this behavior in the future once we have the local scm fully implemented

Potential improvement

Signed-off-by: Olblak <me@olblak.com>
@ghost
Copy link

ghost commented Feb 24, 2023

👇 Click on the image for a new way to code review

Review these changes using an interactive CodeSee Map

Legend

CodeSee Map legend

@olblak olblak enabled auto-merge (squash) February 24, 2023 20:49
@olblak olblak added bug Something isn't working scm-github SCM of type GiHhub scm-git SCM of kind "Git" scm-gittea labels Feb 24, 2023
@olblak olblak merged commit efd246c into updatecli:main Feb 24, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working scm-git SCM of kind "Git" scm-github SCM of type GiHhub scm-gittea
Projects
None yet
Development

Successfully merging this pull request may close these issues.

When using git scm with push=false only the last target is left committed
1 participant