The activeRevisionsMode is forcibly set to Multiple.

[Bug]
In the defaul, the activeRevisionsMode of the revision is set to Single. However, when the GitHub action be executed, it is forced to change to Multiple.

[Solution]
1. If revsion's activeRevisionsMode is Single, GitHub action exits with an error.
2. As a warning, the above logic should be stated to the user.
For me, I think No.1 is better.

Start by locating the GitHub Action entry point that reads or changes the revision's activeRevisionsMode, then trace how Azure Container Apps revisions are configured. Check the existing action tests or validation workflow, if present. Done means Single mode is handled according to the chosen error or warning behavior rather than being silently changed to Multiple.

Written by the indexing model from the issue text.