-
Notifications
You must be signed in to change notification settings - Fork 39
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
[WIP] Unclutter commit monitor #405
base: master
Are you sure you want to change the base?
Conversation
ea050c2
to
1d2dbe6
Compare
First 2 commits are flattening the commit_range directory. The last commit is the big change to the CommitMonitor |
Did a quick first pass on testing and something is wrong. It seems to execute all of the handlers even if there haven't been any changes to the branch. I must have removed a check somewhere in all those deletions. No issues though when the actual workers run. |
This pull request is not mergeable. Please rebase and repush. |
1d2dbe6
to
879a668
Compare
Checked commits Fryguy/miq_bot@b30558e~...879a668 with ruby 2.3.3, rubocop 0.52.1, haml-lint 0.20.0, and yamllint 1.10.0 **
app/workers/commit_monitor.rb
app/workers/commit_monitor_handlers/bugzilla_commenter.rb
app/workers/commit_monitor_handlers/bugzilla_pr_checker.rb
app/workers/commit_monitor_handlers/github_pr_commenter/diff_filename_checker.rb
app/workers/commit_monitor_handlers/path_based_labeler.rb
app/workers/commit_monitor_handlers/rubocop_checker.rb
app/workers/commit_monitor_handlers/rubocop_checker/message_builder.rb
app/workers/commit_monitor_handlers/rubocop_checker/rubocop_results_filter.rb
spec/workers/commit_monitor_handlers/github_pr_commenter/diff_content_checker_spec.rb
spec/workers/commit_monitor_handlers/rubocop_checker/data/with_lines_not_in_the_diff/example.rb
spec/workers/commit_monitor_handlers/rubocop_checker/data/with_results_generating_multiple_comments/lots_of_issues.rb
|
...continued
spec/workers/commit_monitor_handlers/rubocop_checker/data/with_results_with_offenses/coding_convention.rb
spec/workers/commit_monitor_handlers/rubocop_checker/data/with_results_with_offenses/ruby_syntax_error.rb
spec/workers/commit_monitor_handlers/rubocop_checker/data/with_results_with_offenses/ruby_warning.rb
spec/workers/commit_monitor_handlers/rubocop_checker/data/with_void_warnings_in_spec_files/non_spec_file_with_void_warning.rb spec/workers/commit_monitor_handlers/rubocop_checker/data/with_void_warnings_in_spec_files/spec/non_spec_file_in_spec_dir_with_void_warning.rb spec/workers/commit_monitor_handlers/rubocop_checker/message_builder_spec.rb
|
This pull request is not mergeable. Please rebase and repush. |
This pull request has been automatically closed because it has not been updated for at least 3 months. Feel free to reopen this pull request if these changes are still valid. Thank you for all your contributions! More information about the ManageIQ triage process can be found in the triage process documentation. |
Reopening cause I still think this is the right approacj |
This pull request is not mergeable. Please rebase and repush. |
This PR unclutters the core of the CommitMonitor by removing the whole categorization notion of separate workers. All workers will receive the branch_id and the new_commits on that branch, and it is up to the worker how they want to deal with that.
@bdunne Please review.
PR is WIP because I haven't tested enough yet.