Skip to content

fix(i18n): Fix typo in gallery unsupported file message - #17876

Merged
AndyScherzinger merged 1 commit into
masterfrom
rakekniven-patch-2
Oct 28, 2026
Merged

AndyScherzinger merged 1 commit into
masterfrom
rakekniven-patch-2

Conversation

@rakekniven

Copy link
Copy Markdown
Member

Reported at Transifex

Reported at Transifex

Signed-off-by: rakekniven <2069590+rakekniven@users.noreply.github.com>
@github-actions

Copy link
Copy Markdown

Codacy

SpotBugs

CategoryBaseNew
Bad practice2424
Correctness5151
Dodgy code158158
Experimental11
Malicious code vulnerability11
Multithreaded correctness2020
Performance2828
Security1515
Total298298

@github-actions

Copy link
Copy Markdown

📱 QA build

Download app-qa-debug.apk
QR code Open the QR code for this download
Commit 7cc0c88
Version 17876
Available until 7 days after this build

The QA build installs alongside a released Nextcloud app, so you can keep
using your existing install while testing.

Downloading the file requires a GitHub account, so open this link on the
device you want to test on, or transfer the APK to it.

@codecov

codecov Bot commented Oct 25, 2026

Copy link
Copy Markdown

Codecov Report

✅ All modified and coverable lines are covered by tests.

📢 Thoughts on this report? Let us know!

@rakekniven

Copy link
Copy Markdown
Member Author

Failed check says:

Run scripts/analysis/detectWrongSettings.sh
Library commit not within last 10 hashes, please rebase!

@AndyScherzinger
I am not allowed to rebase.

@AndyScherzinger

Copy link
Copy Markdown
Member

/backport to stable-35.0.1

@AndyScherzinger

Copy link
Copy Markdown
Member

/backport to stable-35.0.x

@AndyScherzinger

Copy link
Copy Markdown
Member

/backport to stable-34.1.x

@AndyScherzinger

Copy link
Copy Markdown
Member

/backport to stable-34.0.x

@AndyScherzinger

Copy link
Copy Markdown
Member

/backport to stable-33.1.x

@AndyScherzinger

Copy link
Copy Markdown
Member

/backport to stable-3.36

@AndyScherzinger

Copy link
Copy Markdown
Member

/backport to stable-3.35.x

@AndyScherzinger
AndyScherzinger merged commit e511768 into master Oct 28, 2026
25 of 26 checks passed
@AndyScherzinger
AndyScherzinger deleted the rakekniven-patch-2 branch October 28, 2026 19:33
@backportbot

backportbot Bot commented Oct 28, 2026

Copy link
Copy Markdown

The backport to stable-3.35.x failed. Please do this backport manually.

# Switch to the target branch and update it
git checkout stable-3.35.x
git pull origin stable-3.35.x

# Create the new backport branch
git checkout -b backport/17876/stable-3.35.x

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

# Push the cherry pick commit to the remote repository and open a pull request
git push origin backport/17876/stable-3.35.x

Error: Failed to check for changes with origin/stable-3.35.x: 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 Oct 28, 2026

Copy link
Copy Markdown

The backport to stable-3.36 failed. Please do this backport manually.

# Switch to the target branch and update it
git checkout stable-3.36
git pull origin stable-3.36

# Create the new backport branch
git checkout -b backport/17876/stable-3.36

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

# Push the cherry pick commit to the remote repository and open a pull request
git push origin backport/17876/stable-3.36

Error: Failed to check for changes with origin/stable-3.36: No changes found in backport branch


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

@AndyScherzinger AndyScherzinger added this to the Nextcloud App 35.1.0 milestone Oct 28, 2026
@backportbot

backportbot Bot commented Oct 28, 2026

Copy link
Copy Markdown

The backport to stable-33.1.x failed. Please do this backport manually.

# Switch to the target branch and update it
git checkout stable-33.1.x
git pull origin stable-33.1.x

# Create the new backport branch
git checkout -b backport/17876/stable-33.1.x

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

# Push the cherry pick commit to the remote repository and open a pull request
git push origin backport/17876/stable-33.1.x

Error: Failed to check for changes with origin/stable-33.1.x: 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 Oct 28, 2026

Copy link
Copy Markdown

The backport to stable-34.0.x failed. Please do this backport manually.

# Switch to the target branch and update it
git checkout stable-34.0.x
git pull origin stable-34.0.x

# Create the new backport branch
git checkout -b backport/17876/stable-34.0.x

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

# Push the cherry pick commit to the remote repository and open a pull request
git push origin backport/17876/stable-34.0.x

Error: Failed to check for changes with origin/stable-34.0.x: 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 Oct 28, 2026

Copy link
Copy Markdown

The backport to stable-34.1.x failed. Please do this backport manually.

# Switch to the target branch and update it
git checkout stable-34.1.x
git pull origin stable-34.1.x

# Create the new backport branch
git checkout -b backport/17876/stable-34.1.x

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

# Push the cherry pick commit to the remote repository and open a pull request
git push origin backport/17876/stable-34.1.x

Error: Failed to check for changes with origin/stable-34.1.x: 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 Oct 28, 2026

Copy link
Copy Markdown

The backport to stable-35.0.x failed. Please do this backport manually.

# Switch to the target branch and update it
git checkout stable-35.0.x
git pull origin stable-35.0.x

# Create the new backport branch
git checkout -b backport/17876/stable-35.0.x

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

# Push the cherry pick commit to the remote repository and open a pull request
git push origin backport/17876/stable-35.0.x

Error: Failed to check for changes with origin/stable-35.0.x: 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 Oct 28, 2026

Copy link
Copy Markdown

The backport to stable-35.0.1 failed. Please do this backport manually.

# Switch to the target branch and update it
git checkout stable-35.0.1
git pull origin stable-35.0.1

# Create the new backport branch
git checkout -b backport/17876/stable-35.0.1

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

# Push the cherry pick commit to the remote repository and open a pull request
git push origin backport/17876/stable-35.0.1

Error: Failed to check for changes with origin/stable-35.0.1: No changes found in backport branch


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

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.

2 participants