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.

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

Bump CS Fixer rules to follow latest Nextcloud standards #39271

Merged
merged 3 commits into from
Nov 23, 2023

Conversation

Altahrim
Copy link
Collaborator

Summary

Update PHP CS coding standards to lastest Nextcloud standards

@Altahrim Altahrim self-assigned this Jul 10, 2023
@skjnldsv skjnldsv added this to the Nextcloud 29 milestone Jul 11, 2023
@come-nc come-nc self-requested a review July 17, 2023 10:11
Copy link
Contributor

@come-nc come-nc left a comment

Choose a reason for hiding this comment

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

I think you should also change platform to php: 8.0 in the same composer.json file

@come-nc
Copy link
Contributor

come-nc commented Jul 17, 2023

It seems CI is checking all files so you will have to run cs:fix and commit the result.

@Altahrim Altahrim force-pushed the bump-coding-standards branch 2 times, most recently from 5d8d31b to f71689f Compare July 18, 2023 09:45
@Altahrim Altahrim marked this pull request as ready for review July 18, 2023 09:46
@Altahrim Altahrim added 3. to review Waiting for reviews and removed 2. developing Work in progress labels Jul 18, 2023
@Altahrim Altahrim added 4. to release Ready to be released and/or waiting for tests to finish and removed 3. to review Waiting for reviews labels Jul 19, 2023
@come-nc
Copy link
Contributor

come-nc commented Jul 20, 2023

@skjnldsv You’ve put milestone 29 for this on purpose? Does it mean we should wait for 28 branch off before merging?

@ChristophWurst ChristophWurst removed their request for review July 21, 2023 08:00
@nickvergessen
Copy link
Member

Does it mean we should wait for 28 branch off before merging?

The current idea is to do and merge it directly before the branch-off to break as few PRs as possible and to be still able to somewhat normally use the backport bot to stable28 then

@come-nc come-nc mentioned this pull request Sep 26, 2023
13 tasks
@Altahrim Altahrim force-pushed the bump-coding-standards branch 2 times, most recently from 3c76d84 to bb941d1 Compare September 28, 2023 09:50
@nickvergessen
Copy link
Member

Now is the time

@nickvergessen
Copy link
Member

rebasing with dropping the cs:fix and running it afterwards again

github-advanced-security[bot]

This comment was marked as off-topic.

Altahrim and others added 3 commits November 23, 2023 10:36
…red itself

Signed-off-by: Joas Schilling <[email protected]>
Signed-off-by: Benjamin Gaussorgues <[email protected]>
Signed-off-by: Joas Schilling <[email protected]>
Signed-off-by: Benjamin Gaussorgues <[email protected]>
@nickvergessen nickvergessen merged commit 3d814b0 into master Nov 23, 2023
61 of 62 checks passed
@nickvergessen nickvergessen deleted the bump-coding-standards branch November 23, 2023 10:40
@blizzz blizzz mentioned this pull request Nov 23, 2023
5 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
4. to release Ready to be released and/or waiting for tests to finish enhancement
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants