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
refactor: migrate schedules_processor
to use python-gitlab
#706
Conversation
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## main #706 +/- ##
==========================================
+ Coverage 85.38% 85.59% +0.21%
==========================================
Files 70 69 -1
Lines 2784 2770 -14
==========================================
- Hits 2377 2371 -6
+ Misses 407 399 -8
|
f38f674
to
1d5698d
Compare
1d5698d
to
ee6fd7f
Compare
ee6fd7f
to
92082d7
Compare
92082d7
to
1a8d178
Compare
Thanks for this PR @TimKnight-Opencast . Based on PR description and file changes, it seems branch protection processor is also included. Really appreciate the help converting both schedule processor and branch protection processor. But, it's a lot easier to review and safer if we keep the scope of changes to minimum. Could you please open a separate PR for branch protection processor related changes? |
schedules_processor
to use python-gitlab
1a8d178
to
17893a2
Compare
@amimas done I've cut a new branch for branch_processor changes. Will raise a PR once the group_members refactor is in so can re-use the common python-gitlab code I'm adding in there |
(same person, I just work for a consultancy at DWP, and due to stuff, needed to contribute from this account instead last week 😸 ) |
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.
It mostly looks good to me. Thanks for taking care of this. Only major issue I see is how the schedule is being created/updated.
@amimas - reverted the test changes so it's just a subset using project_for_function (i.e. my new tests) and added that test for validating the logs when no changes to an existing schedule are made |
Thanks for all the work on this ❤️ . I've re-opened a conversation that I think is not resolved yet and it will likely introduce bug. Otherwise it looks good to merge. |
- tests currently don't clear down schedules after, so to avoid conflicts/mutations during test run, always use a fresh project
This reverts commit e27119d.
f30f693
to
67acbc0
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.
Looks good to me. Thanks again for all the work.
schedules
configuration feature to use python-gitlab library #631