Skip to content

Add documentation on advanced settings->reverb preset - #1153

Open
dingodoppelt wants to merge 4 commits into
jamulussoftware:next-releasefrom
dingodoppelt:reverb_presets
Open

dingodoppelt wants to merge 4 commits into
jamulussoftware:next-releasefrom
dingodoppelt:reverb_presets

Conversation

@dingodoppelt

@dingodoppelt dingodoppelt commented Jul 19, 2026

Copy link
Copy Markdown
Member

Short description of changes
Documents Advanced Settings -> Reverb Preset

Context: Fixes an issue? Related issues
jamulussoftware/jamulus#3787

Status of this Pull Request

What is missing until this pull request can be merged?

Does this need translation?
Yes

Checklist

  • I've verified that this Pull Request follows the general code principles
  • I waited some time after this Pull
    Request was opened and all GitHub checks completed without errors.
  • I'm sure that this Pull Request goes to the correct branch
advanced-settings

Comment thread wiki/en/Software-Manual.md Outdated
@dingodoppelt
dingodoppelt marked this pull request as draft July 20, 2026 07:59
@pljones pljones added this to Tracking Jul 20, 2026
@github-project-automation github-project-automation Bot moved this to Triage in Tracking Jul 20, 2026
@pljones

pljones commented Jul 20, 2026

Copy link
Copy Markdown
Contributor

That ...jamulus.io would need re-screenshot-ing to ...jamulus.app.

@pljones

pljones commented Jul 22, 2026

Copy link
Copy Markdown
Contributor

Can you try rebasing to a refetched upstream, please.

@dingodoppelt

Copy link
Copy Markdown
Member Author

Can you try rebasing to a refetched upstream, please.

This is already rebased on next-release. I guess only another commit would trigger the fixed workflow?

@pljones

pljones commented Jul 22, 2026

Copy link
Copy Markdown
Contributor

OK, so the automagick upmerge from release to next-release didn't work for Jekyll... I don't have time to check it today, unfortunately.

@pljones

pljones commented Jul 25, 2026

Copy link
Copy Markdown
Contributor

Right, I think rebasing now should work. It should be based off commit dd096f2 (if I read it right).

git checkout next-release
git pull upstream next-release
git push
git checkout -
git rebase -i next-release ;# and check it's just your branch commit(s)

@dingodoppelt
dingodoppelt marked this pull request as ready for review August 10, 2026 07:53

This branch has not been deployed

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

Labels

None yet

Projects

Status: Triage

Development

Successfully merging this pull request may close these issues.

3 participants