Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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
Issue5 #6
Issue5 #6
Changes from all commits
39b8e31
f34c2b4
db083c7
a8f9256
5679fa0
e75f58f
bd442cb
6840573
eac81b0
3fac1a2
941c445
1272f3a
01a28d7
e9e40c2
b6c42d5
18084ee
e981f6c
9c856a6
16bbca3
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I just got the following output when I accidentally ran cleanup on a repository that was already cleaned:
It looks like the error (
abort: repository is unrelated
) still had the exit code of 0 (no commits to pull) and the script continued with cloning the official repository. Should we check for this?There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I wouldn't bother. This is not a script meant to be run by many people many times, and we cannot predict all user errors. I think users that make this error are likely to find out eventually what went wrong, so all this would do is potentially save them a bit of time.
Also, we should merge this soon; as far as I understand, the main branch is still on code that does no reordering and is not likely to work.