-
Notifications
You must be signed in to change notification settings - Fork 486
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: add subtask register for github plugin #5411
Conversation
7995418
to
adbe570
Compare
e6505bb
to
9efb91f
Compare
Hi @klesh, Should i create pr for each plugin to add this register, or do this in one pr ? |
@@ -44,6 +48,7 @@ var CollectApiPullRequestCommitsMeta = plugin.SubTaskMeta{ | |||
EnabledByDefault: true, | |||
Description: "Collect PullRequestCommits data from Github api, supports both timeFilter and diffSync.", | |||
DomainTypes: []string{plugin.DOMAIN_TYPE_CROSS, plugin.DOMAIN_TYPE_CODE_REVIEW}, | |||
Dependencies: []*plugin.SubTaskMeta{&ExtractApiEventsMeta}, |
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 realize that the Dependencies
are defined based on the current order which would work but is not accurate.
For example, the CollectApiPullRequestCommitsMeta
should depend on the ExtractApiPullRequestMete
instead of ExtractApiEventsMeta
.
Would you mind updating the code to reflect that? The trick is to identify which table is required in the collector as the Input
parameter, and find out the Extractor of the table.
Hi, @chenggui53 , thanks for asking. I think both are fine for this refactor. BTW, Your contribution means a lot to the project, would you like to join us as an Apache Committer? |
@klesh Your comments are very helpful, this register is a step forward, I will fix this part as soon as possible. |
2c44c4a
to
c570292
Compare
Nice, I will nominate you ASAP, it may take a couple of weeks. |
a67bbfd
to
a4aa5e0
Compare
@chenggui53 I thought we agree on "One PR for Plugin" so I can help verify the dependencies are correct. Seems like this PR contains multiple plugins. |
@klesh sorry, i've modified multiple plugins in this branch for test,it's not ready for review. i will create a new branch for test and request your review as it done |
0e2daef
to
3e3eda0
Compare
c1b138d
to
604d771
Compare
d902ac3
to
416fcbd
Compare
@chenggui53 Seems ready to merge, am I right? |
@klesh Yes, I think so. |
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.
LGTM
* refactor: add subtask registert for github * refactor: add subtask register * refactor: add subtask register * refactor: add subtask register * refactor: add subtask register * refactor: add subtask register * refactor: add subtask register * refactor: add subtask register * refactor: add subtask register * refactor: add subtask register * refactor: add subtask register * refactor: add subtask register * refactor: add subtask register * refactor: add subtask register * refactor: add subtask register * refactor: add subtask register * refactor: add subtask meta register * refactor: add subtask register * refactor: add subtask register * refactor: add subtask register * refactor: Update remote.go * refactor: add subtask register * refactor: add subtask register * refactor: add subtask register * refactor: add subtask register * refactor: add subtask register * refactor: update subtask register * refactor: update subtask register * refactor: add subtask register * refactor: add subtask register * refactor: add subtask register
pr-type/bug-fix
,pr-type/feature-development
, etc.Summary
What does this PR do?
like pr #4896, add subtask register for github
Does this close any open issues?
Closes #4413
Screenshots
Include any relevant screenshots here.
Other Information
Any other information that is important to this PR.