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

Consider adding custom checkout action #28

Open
ylobankov opened this issue Nov 8, 2022 · 1 comment
Open

Consider adding custom checkout action #28

ylobankov opened this issue Nov 8, 2022 · 1 comment

Comments

@ylobankov
Copy link
Contributor

We should consider adding the own checkout action. The default action fails from time to time [1, 2] and lacks parallel submodules update. To resolve the issue [1] we developed the cleanup action, but this functionality can be added to the new action under the corresponding option.

[1] tarantool/tarantool-qa#145
[2] tarantool/tarantool-qa#261

@NickVolynkin
Copy link
Contributor

I propose that this action should have the same set of parameters as actions/checkout, or a superset of them. This way we'll be able to replace the basic action easily.

NickVolynkin added a commit that referenced this issue Nov 10, 2022
Make an empty detached commit for actions/checkout to properly
clean the project's workspace before checking out new code
revision.

Part of #28
Related to tarantool/tarantool-qa#145
NickVolynkin added a commit that referenced this issue Nov 10, 2022
Make an empty detached commit for actions/checkout to properly
clean the project's workspace before checking out new code
revision.

Part of #28
Related to tarantool/tarantool-qa#145
NickVolynkin added a commit that referenced this issue Nov 10, 2022
Make an empty detached commit for actions/checkout to properly
clean the project's workspace before checking out new code
revision.

Part of #28
Related to tarantool/tarantool-qa#145
NickVolynkin added a commit that referenced this issue Nov 10, 2022
Make an empty detached commit for actions/checkout to properly
clean the project's workspace before checking out new code
revision. It makes the actions/checkout resilient to
various problems related to git submodules.

Part of #28
Related to tarantool/tarantool-qa#145
NickVolynkin added a commit that referenced this issue Nov 10, 2022
Make an empty detached commit for actions/checkout to properly
clean the project's workspace before checking out new code
revision. It makes the actions/checkout resilient to
various problems related to git submodules.

Part of #28
Related to tarantool/tarantool-qa#145
NickVolynkin added a commit that referenced this issue Nov 10, 2022
Make an empty detached commit for actions/checkout to properly
clean the project's workspace before checking out new code
revision. It makes the actions/checkout resilient to
various problems related to git submodules.

Part of #28
Related to tarantool/tarantool-qa#145
NickVolynkin added a commit that referenced this issue Nov 10, 2022
Make an empty detached commit for actions/checkout to properly
clean the project's workspace before checking out new code
revision. It makes the actions/checkout resilient to
various problems related to git submodules.

Part of #28
Related to tarantool/tarantool-qa#145
NickVolynkin added a commit that referenced this issue Nov 10, 2022
Make an empty detached commit for actions/checkout to properly
clean the project's workspace before checking out new code
revision. It makes the actions/checkout resilient to
various problems related to git submodules.

Part of #28
Related to tarantool/tarantool-qa#145
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants