Skip to content

fix: disable ghostbuster for normal use and encapsulate into own rake task #103

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
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

rwaffen
Copy link
Member

@rwaffen rwaffen commented Mar 17, 2025

fixes: #101

@rwaffen rwaffen added the bug Something isn't working label Mar 17, 2025
@rwaffen rwaffen requested a review from a team as a code owner March 17, 2025 10:37
@rwaffen rwaffen marked this pull request as draft March 17, 2025 10:37
@rwaffen
Copy link
Member Author

rwaffen commented Mar 17, 2025

this is a draft because had no time to test it yet, but wanted to write down my thoughts

@@ -27,5 +43,24 @@ namespace :voxpupuli do

Rake::Task[:lint].invoke
end

desc 'Who you gonna call? Ghostbusters!'
task :ghostbuster do
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

maybe add a test to the pipeline that checks if the rake task exists?

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

some more testing would be nice here :D
will check what i can do about it.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
Status: No status
Development

Successfully merging this pull request may close these issues.

Bug: ghostbuster linters are executed every time
2 participants