Skip to content

Merge branch 'master' into fullscreen#1

Open
mvbmonsterenergi-tech wants to merge 3 commits into
masterfrom
fullscreen
Open

Merge branch 'master' into fullscreen#1
mvbmonsterenergi-tech wants to merge 3 commits into
masterfrom
fullscreen

Conversation

@mvbmonsterenergi-tech
Copy link
Copy Markdown
Owner

@mvbmonsterenergi-tech mvbmonsterenergi-tech commented Feb 17, 2026

requests should follow the git flow described in the wiki.
To get git history clean and aid in more useful release notes, it is essential to use the Squash and merge option when
merging into 'master', and the Create merge commit option when merging into 'releases'.

What changes does this PR introduce?

Any background context you want to provide?

Where should the reviewer start?

Has this been manually tested? How?

What value does this provide to our end users?

What GIF best describes this PR or how it makes you feel?

@mvbmonsterenergi-tech mvbmonsterenergi-tech changed the base branch from cloud-demo to apps-in-assets February 18, 2026 06:08
@mvbmonsterenergi-tech mvbmonsterenergi-tech changed the base branch from apps-in-assets to cloud February 20, 2026 09:10
@mvbmonsterenergi-tech mvbmonsterenergi-tech changed the base branch from cloud to master February 20, 2026 12:23
@mvbmonsterenergi-tech mvbmonsterenergi-tech changed the base branch from master to corbinlc-patch-1 March 3, 2026 15:32
Repository owner locked and limited conversation to collaborators Mar 3, 2026
Repository owner unlocked this conversation Mar 3, 2026
@mvbmonsterenergi-tech mvbmonsterenergi-tech changed the base branch from corbinlc-patch-1 to master March 3, 2026 23:00
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants