Skip to content
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.

Sign up for GitHub

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

Jump to bottom

t: Use consistent 'Mojo::Base' instead of strict+warnings #5403

Merged
merged 1 commit into from
Dec 20, 2023
Merged

t: Use consistent 'Mojo::Base' instead of strict+warnings #5403

merged 1 commit into from
Dec 20, 2023

Conversation

okurz
Copy link
Member

@okurz okurz commented Dec 20, 2023 •
edited
Loading

Same as suggested in our documentation we should use Mojo::Base
consistently in openQA test modules which we only have a single one of
within this repository.

Motivated by:

@okurz
t: Use consistent 'Mojo::Base' instead of strict+warnings
f594ffa 
Same as suggested in our documentation we should use Mojo::Base
consistently in openQA test modules which we only have a single one of
within this repository.
@okurz okurz mentioned this pull request Dec 20, 2023
Open
@mergify mergify bot merged commit 0c7cd29 into os-autoinst:master Dec 20, 2023
36 checks passed
@okurz okurz deleted the feature/mojo_base branch December 20, 2023 13:53
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers

@kalikiana kalikiana kalikiana approved these changes

@Martchus Martchus Martchus approved these changes

Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
3 participants
@okurz @kalikiana @Martchus