-
Notifications
You must be signed in to change notification settings - Fork 74
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
(Git-6) Use new Git Backend in Entire auto_tick flow #3004
Conversation
@0xbe7a I think this is worth reviewing, even with limited knowledge of the codebase |
683b402
to
4c553c4
Compare
Codecov ReportAttention: Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## main #3004 +/- ##
==========================================
+ Coverage 76.15% 77.01% +0.86%
==========================================
Files 120 120
Lines 12942 13201 +259
==========================================
+ Hits 9856 10167 +311
+ Misses 3086 3034 -52 ☔ View full report in Codecov by Sentry. |
d29da4a
to
456c237
Compare
Matt, FYI: Bela is no longer mentoring me, therefore I ping @pavelzw for an additional review. |
5d896cf
to
1415cee
Compare
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 left some comments. One todo item is to search the code base for any functions you have removed to ensure they are not used anywhere else.
0448fcd
to
c37ea4f
Compare
Thank you! I just verified that no removed function is used in the regro or conda-forge organization via a quick GitHub search. |
We're seeing errors in pushing to repos with this so I am going to revert. |
Description:
Building upon #3003, this replaces the remaining auto_tick logic to use the new git backend.
Notably, this PR ensures that the new backend is used for opening PRs and commenting on PRs.
Checklist:
Cross-refs, links to issues, etc:
#3003 should be merged first.