Skip to content

stable32: Fix incorrect heading markup in example_centos.rst#13636

Merged
joshtrichards merged 1 commit into
nextcloud:stable32from
brlin-tw:patch/fix-incorrect-heading-markup-in-centos8-install-example-stable32
Apr 17, 2026
Merged

stable32: Fix incorrect heading markup in example_centos.rst#13636
joshtrichards merged 1 commit into
nextcloud:stable32from
brlin-tw:patch/fix-incorrect-heading-markup-in-centos8-install-example-stable32

Conversation

@brlin-tw

@brlin-tw brlin-tw commented Sep 9, 2025

Copy link
Copy Markdown
Contributor

☑️ Resolves

Fixes #13633 for stable32.

🖼️ Screenshots

image

@brlin-tw brlin-tw changed the title Fix incorrect heading markup in example_centos.rst stable31: Fix incorrect heading markup in example_centos.rst Sep 9, 2025
@brlin-tw brlin-tw changed the title stable31: Fix incorrect heading markup in example_centos.rst stable32: Fix incorrect heading markup in example_centos.rst Sep 9, 2025

@joshtrichards joshtrichards left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

Thanks.l! For future reference, you should be able to just make the change once (against the master branch). Once that is merged you/any of us can trigger the backport port for relevant older branches to generate PRs automatically with the change. ;-)

@github-actions

Copy link
Copy Markdown
Contributor

Hello there,
Thank you so much for taking the time and effort to create a pull request to our Nextcloud project.

We hope that the review process is going smooth and is helpful for you. We want to ensure your pull request is reviewed to your satisfaction. If you have a moment, our community management team would very much appreciate your feedback on your experience with this PR review process.

Your feedback is valuable to us as we continuously strive to improve our community developer experience. Please take a moment to complete our short survey by clicking on the following link: https://cloud.nextcloud.com/apps/forms/s/i9Ago4EQRZ7TWxjfmeEpPkf6

Thank you for contributing to Nextcloud and we hope to hear from you soon!

(If you believe you should not receive this message, you can add yourself to the blocklist.)

@brlin-tw

Copy link
Copy Markdown
Contributor Author

@joshtrichards

Thanks.l! For future reference, you should be able to just make the change once (against the master branch). Once that is merged you/any of us can trigger the backport port for relevant older branches to generate PRs automatically with the change. ;-)

Gotcha. Thanks for the heads-up!

@rakekniven rakekniven force-pushed the patch/fix-incorrect-heading-markup-in-centos8-install-example-stable32 branch from 702b021 to 5aa3981 Compare October 14, 2025 13:23
@rakekniven rakekniven force-pushed the patch/fix-incorrect-heading-markup-in-centos8-install-example-stable32 branch from 5aa3981 to 82cfd2c Compare November 17, 2025 13:39
@Altahrim Altahrim removed this from the Nextcloud 32.0.6 milestone Feb 12, 2026
@Altahrim Altahrim added this to the Nextcloud 32.0.7 milestone Feb 12, 2026
@skjnldsv skjnldsv force-pushed the patch/fix-incorrect-heading-markup-in-centos8-install-example-stable32 branch from 82cfd2c to ca8ef6f Compare April 17, 2026 07:23
Fixes nextcloud#13633.

Signed-off-by: 林博仁(Buo-ren Lin) <buo.ren.lin@gmail.com>
@skjnldsv skjnldsv force-pushed the patch/fix-incorrect-heading-markup-in-centos8-install-example-stable32 branch from ca8ef6f to dbcb357 Compare April 17, 2026 07:54
@joshtrichards joshtrichards merged commit eacddce into nextcloud:stable32 Apr 17, 2026
16 checks passed
@skjnldsv

Copy link
Copy Markdown
Member

/backport to stable33

@skjnldsv

Copy link
Copy Markdown
Member

/backport to master

@backportbot

backportbot Bot commented Apr 17, 2026

Copy link
Copy Markdown

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

# Switch to the target branch and update it
git checkout stable33
git pull origin stable33

# Create the new backport branch
git checkout -b backport/13636/stable33

# Cherry pick the change from the commit sha1 of the change against the default branch
# This might cause conflicts, resolve them
git cherry-pick dbcb357e

# Push the cherry pick commit to the remote repository and open a pull request
git push origin backport/13636/stable33

Error: Failed to check for changes with origin/stable33: No changes found in backport branch


Learn more about backports at https://docs.nextcloud.com/server/stable/go.php?to=developer-backports.

@backportbot

backportbot Bot commented Apr 17, 2026

Copy link
Copy Markdown

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

# Switch to the target branch and update it
git checkout master
git pull origin master

# Create the new backport branch
git checkout -b backport/13636/master

# Cherry pick the change from the commit sha1 of the change against the default branch
# This might cause conflicts, resolve them
git cherry-pick dbcb357e

# Push the cherry pick commit to the remote repository and open a pull request
git push origin backport/13636/master

Error: Failed to check for changes with origin/master: No changes found in backport branch


Learn more about backports at https://docs.nextcloud.com/server/stable/go.php?to=developer-backports.

@skjnldsv

Copy link
Copy Markdown
Member

Ah, backports were already done 👍

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

6 participants