-
Notifications
You must be signed in to change notification settings - Fork 49
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
Draft: GitLab events / parsing refactoring #2590
base: main
Are you sure you want to change the base?
Conversation
feb7e0e
to
9a8f285
Compare
Build failed. ✔️ pre-commit SUCCESS in 2m 16s |
@majamassarini @lbarcziova WDYT? At the moment it's broken everywhere possible :D it looks like we have also some pretty intrusive mocking in place, so this reshuffle opened the can of worms… I still haven't made up my mind about the usage of the events, cause they can be imported as from packit_service.worker.events.github.pr import Synchronize but at the same time I have a feeling that it won't look very good once it gets mixed up with the other forges, for now I replaced the imports with |
Tip I had a feeling something will crawl out, when I make
|
Build failed. ✔️ pre-commit SUCCESS in 2m 19s |
Build failed. ✔️ pre-commit SUCCESS in 2m 15s |
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.
the structure looks good to me 🚀
for now I replaced the imports with as ‹original_name›, so that it breaks as least stuff as possible, but going forward it doesn't feel very feasible
agreed it may be a good middle step
97853c1
to
1cd634b
Compare
Build failed. ✔️ pre-commit SUCCESS in 2m 12s |
Thanks for starting this big refactoring, to me it looks good! from packit_service.worker.events.github.pr import Synchronize and use instead the namespaces we have created from packit_service.worker.events import github, gitlab, pagure
[...]
github.pr.Synchronize
[...]
gitlab.pr.Synchronize So I think the hierarchy is fine 🤔 |
oh i see, so you really wanna use it like that 😁 I was a bit worried how explicit it will be, but I guess it's better edit: BTW I managed to break the mypy locally, it crashes :D but passes in Zuul… |
Build failed. ✔️ pre-commit SUCCESS in 2m 05s |
7f6c114
to
3fa459b
Compare
Build failed. ✔️ pre-commit SUCCESS in 2m 03s |
3fa459b
to
f9e813c
Compare
Build failed. ✔️ pre-commit SUCCESS in 2m 03s |
f9e813c
to
fee2a38
Compare
Build failed. ✔️ pre-commit SUCCESS in 2m 10s |
fee2a38
to
e115f0c
Compare
Build failed. ✔️ pre-commit SUCCESS in 2m 08s |
e115f0c
to
c0c227d
Compare
Build failed. ✔️ pre-commit SUCCESS in 1m 47s |
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 really like how you broke this up into smaller pieces, this is so much more readable, good job!
@@ -463,12 +461,18 @@ def get_dict(self, default_dict: Optional[dict] = None) -> dict: | |||
|
|||
return d | |||
|
|||
# [XXX] Are these supposed to be abstract methods? |
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.
yes, I would say these should be abstract
""" | ||
# [XXX] Is `True` as a default here a good idea? |
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 don't see that as an issue
self.account_id = account_id | ||
self.account_url = account_url | ||
self.account_type = account_type | ||
# repos within the account/namespace |
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.
# repos within the account/namespace | |
# repos within the account/namespace in the scope of the installation |
packit_service/worker/events/koji.py
Outdated
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 to me a good candidate for breaking down as well, but can be done as a followup
Build failed. ✔️ pre-commit SUCCESS in 1m 45s |
Signed-off-by: Matej Focko <[email protected]>
Signed-off-by: Matej Focko <[email protected]>
remove after resolving Signed-off-by: Matej Focko <[email protected]>
Signed-off-by: Matej Focko <[email protected]>
Signed-off-by: Matej Focko <[email protected]>
Signed-off-by: Matej Focko <[email protected]>
Signed-off-by: Matej Focko <[email protected]>
Signed-off-by: Matej Focko <[email protected]>
Signed-off-by: Matej Focko <[email protected]>
Signed-off-by: Matej Focko <[email protected]>
Signed-off-by: Matej Focko <[email protected]>
Signed-off-by: Matej Focko <[email protected]>
Signed-off-by: Matej Focko <[email protected]>
To be consistent with the naming from other modules. Signed-off-by: Matej Focko <[email protected]>
Signed-off-by: Matej Focko <[email protected]>
Signed-off-by: Matej Focko <[email protected]>
Signed-off-by: Matej Focko <[email protected]>
8e6af25
to
8346172
Compare
Build failed. ✔️ pre-commit SUCCESS in 1m 50s |
TODO:
packit/packit.dev
.Fixes
Supersedes #2586 (cause GitHub is a 🫓)
Merge before/after
RELEASE NOTES BEGIN
Packit now supports automatic ordering of ☕ after all checks pass.
RELEASE NOTES END