Skip to content

Conversation

@JuliaKirschenheuter
Copy link
Contributor

Fixes #35138

Copy link
Member

@Pytal Pytal left a comment

Choose a reason for hiding this comment

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

Looks good and seems the global styles keeps them in the same positions

Copy link
Member

@ChristophWurst ChristophWurst left a comment

Choose a reason for hiding this comment

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

Code changes look good

@szaimen
Copy link
Contributor

szaimen commented Nov 15, 2022

/rebase

@ChristophWurst
Copy link
Member

I just restarted Drone. The rebase is not necessary.

Signed-off-by: julia.kirschenheuter <julia.kirschenheuter@nextcloud.com>
@nextcloud-command nextcloud-command force-pushed the fix/fix-33741-h1_should_instead_be_in_the_app_content branch from 48bb1c0 to a8ff2ff Compare November 15, 2022 10:50
@szaimen
Copy link
Contributor

szaimen commented Nov 15, 2022

I just restarted Drone. The rebase is not necessary.

Sorry

@szaimen szaimen added 4. to release Ready to be released and/or waiting for tests to finish and removed 3. to review Waiting for reviews labels Nov 15, 2022
@szaimen szaimen added this to the Nextcloud 26 milestone Nov 15, 2022
@szaimen
Copy link
Contributor

szaimen commented Nov 15, 2022

/backport to stable25

@ChristophWurst
Copy link
Member

Sharing integration test failure unrelated.

@ChristophWurst ChristophWurst merged commit 102617f into master Nov 15, 2022
@ChristophWurst ChristophWurst deleted the fix/fix-33741-h1_should_instead_be_in_the_app_content branch November 15, 2022 15:14
@backportbot-nextcloud
Copy link

The backport to stable25 failed. Please do this backport manually.

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

Projects

None yet

Development

Successfully merging this pull request may close these issues.

h1 should instead be in the app content, ideally displayed visually

5 participants