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

Fix success handling for update_repos #1520

Merged
merged 2 commits into from
Jul 11, 2021
Merged

Fix success handling for update_repos #1520

merged 2 commits into from
Jul 11, 2021

Conversation

bboe
Copy link
Contributor

@bboe bboe commented Jul 10, 2021

As part of the switch to python git, the success case handling was reversed even though 0 was still meant to indicate success (formerly used to represent process exited without error).

89bce02#diff-b279f20d61152a2a99689009a59d70609c92039568c203da8c84bb56ceacd94fR287

This pull request fixes that issue and makes the code a bit more clear by using booleans rather than integers to represent the success state.

bboe and others added 2 commits July 9, 2021 23:02
As part of the switch to python git, the success case handling was reversed even though `0` was still meant to indicate success (formerly used to represent process exited without error).

errbotio@89bce02#diff-b279f20d61152a2a99689009a59d70609c92039568c203da8c84bb56ceacd94fR287

This pull request fixes that issue and makes the code a bit more clear by using booleans rather than integers to represent the success state.
@sijis sijis merged commit 934ba5d into errbotio:master Jul 11, 2021
@sijis
Copy link
Contributor

sijis commented Jul 11, 2021

Thank you!

@bboe bboe deleted the patch-1 branch July 11, 2021 15:11
sijis added a commit that referenced this pull request Jun 11, 2022
* Fix success handling for update_repos

As part of the switch to python git, the success case handling was reversed even though `0` was still meant to indicate success (formerly used to represent process exited without error).

89bce02#diff-b279f20d61152a2a99689009a59d70609c92039568c203da8c84bb56ceacd94fR287

This pull request fixes that issue and makes the code a bit more clear by using booleans rather than integers to represent the success state.

* docs: Add fixes to CHANGES

Co-authored-by: Sijis Aviles <sijis.aviles+github@gmail.com>
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

Successfully merging this pull request may close these issues.

None yet

2 participants