-
-
Notifications
You must be signed in to change notification settings - Fork 4.7k
Use clearer name setUpScenario #3559
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
Conversation
|
@phil-davis, thanks for your PR! By analyzing the history of the files in this pull request, we identified @nickvergessen, @LukasReschke and @ChristophWurst to be potential reviewers. |
ChristophWurst
left a comment
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.
Makes sense! Thanks!
|
Matching change in ownCloud owncloud/core#27189 also |
|
CI drone pr failure: what is that all about? |
|
Please see https://github.com/nextcloud/server#contribution-guidelines. We require all commits to this repository to be signed (using |
Signed-off-by: Phil Davis <[email protected]>
|
This is not going to work like this. Resubmitted as #3566 |
Issue #3558
The name tearUpScenario was confusing when I was looking at how some existing tests were set up. In English, "tear up" is what you do with a printed contract when you do not like it! It is a destructive thing.
Rename it to setUpScenario