Microsoft GH-100 Practice Test 47
Question 460
GitHub Enterprise administration scenario — Keep pull request fork jobs unprivileged. In an enterprise development environment: A public repository's CI loads unreviewed fork code and a new workflow edit would provide the test job with deployment secrets. A controlled enterprise configuration review requires a coherent rationale, approved change and confirmed outcome. Select EXACTLY THREE: the governing GitHub administration principle, the proportionate authorized intervention AND the independently observable outcome for this scenario.
- A fork pull request receives only safe read access and cannot access deployment credentials in a controlled test.
- Pull request code from untrusted forks should run under restricted credentials and cannot be assumed safe because it is in a workflow.
- Separate untrusted validation from privileged deployment and remove secrets from fork-triggered execution contexts.
- Build caches are an input trust boundary and should not carry attacker-influenced execution material into privileged releases.
- Runner group access matches the approved organization list and the change actor is recorded for investigation.
- Restore the supported runner service or replace the failed agent through an approved capacity and image process.
Explanation
Correct Answers
A:A fork pull request receives only safe read access and cannot access deployment credentials in a controlled test. Separate untrusted validation from privileged deployment and remove secrets from fork-triggered execution contexts. Pull request code from untrusted forks should run under restricted credentials and cannot be assumed safe because it is in a workflow.
B:Pull request code from untrusted forks should run under restricted credentials and cannot be assumed safe because it is in a workflow. Separate untrusted validation from privileged deployment and remove secrets from fork-triggered execution contexts. A fork pull request receives only safe read access and cannot access deployment credentials in a controlled test.
C:Separate untrusted validation from privileged deployment and remove secrets from fork-triggered execution contexts. Pull request code from untrusted forks should run under restricted credentials and cannot be assumed safe because it is in a workflow. A fork pull request receives only safe read access and cannot access deployment credentials in a controlled test.
Incorrect Answers
D:Build caches are an input trust boundary and should not carry attacker-influenced execution material into privileged releases. It is not the rule that supports the proposed change and acceptance test: A public repository's CI loads unreviewed fork code and a new workflow edit would provide the test job with deployment secrets. Pull request code from untrusted forks should run under restricted credentials and cannot be assumed safe because it is in a workflow. Separate untrusted validation from privileged deployment and remove secrets from fork-triggered execution contexts.
E:Runner group access matches the approved organization list and the change actor is recorded for investigation. It would not independently demonstrate that the control works: A public repository's CI loads unreviewed fork code and a new workflow edit would provide the test job with deployment secrets. A fork pull request receives only safe read access and cannot access deployment credentials in a controlled test. Separate untrusted validation from privileged deployment and remove secrets from fork-triggered execution contexts.
F:Restore the supported runner service or replace the failed agent through an approved capacity and image process. It does not implement the governing rule for this approval: A public repository's CI loads unreviewed fork code and a new workflow edit would provide the test job with deployment secrets. Separate untrusted validation from privileged deployment and remove secrets from fork-triggered execution contexts. A fork pull request receives only safe read access and cannot access deployment credentials in a controlled test.
Question 461
GitHub Enterprise administration scenario — Guard pull_request_target workflows. In an enterprise development environment: An organization uses pull_request_target to label contributor pull requests but also checks out the contributor's head commit and executes its scripts using a privileged token. The administrator must identify the controlling access, governance or platform principle rather than an unrelated configuration fix. Which principle BEST addresses this condition? Choose ONE best answer.
- Reusable workflow secret passing should be explicit and consistent with the callee's trust boundary and job purpose.
- Privileged workflow triggers require strict separation from untrusted pull request code and controlled checkout targets.
- Runner capacity and queue telemetry should determine scaling actions instead of broad permission exceptions.
- Workflow templates aid adoption but do not alone prove mandatory enterprise policy enforcement.
Explanation
Correct Answer
B:Privileged workflow triggers require strict separation from untrusted pull request code and controlled checkout targets. Trace the workflow's event context, checked-out ref, executed commands, token permission and available secrets. Retain only safe metadata operations in the privileged workflow and move fork-code tests into isolated low-privilege jobs.
Incorrect Answers
A:Reusable workflow secret passing should be explicit and consistent with the callee's trust boundary and job purpose. It does not govern the condition described: An organization uses pull_request_target to label contributor pull requests but also checks out the contributor's head commit and executes its scripts using a privileged token. Privileged workflow triggers require strict separation from untrusted pull request code and controlled checkout targets.
C:Runner capacity and queue telemetry should determine scaling actions instead of broad permission exceptions. It does not govern the condition described: An organization uses pull_request_target to label contributor pull requests but also checks out the contributor's head commit and executes its scripts using a privileged token. Privileged workflow triggers require strict separation from untrusted pull request code and controlled checkout targets.
D:Workflow templates aid adoption but do not alone prove mandatory enterprise policy enforcement. It does not govern the condition described: An organization uses pull_request_target to label contributor pull requests but also checks out the contributor's head commit and executes its scripts using a privileged token. Privileged workflow triggers require strict separation from untrusted pull request code and controlled checkout targets.
Question 462
GitHub Enterprise administration scenario — Guard pull_request_target workflows. In an enterprise development environment: An organization uses pull_request_target to label contributor pull requests but also checks out the contributor's head commit and executes its scripts using a privileged token. Before changing enterprise policies, permissions or workflows, which diagnostic check BEST establishes the decisive fact? Choose ONE best answer.
- Inspect triggers, concurrency group expressions, active run histories and the deployment service's rollback behavior.
- Trace the workflow's event context, checked-out ref, executed commands, token permission and available secrets.
- Check the secret's selected-repository visibility settings and every workflow currently referencing it.
- Inspect the workflow YAML expression, job shell and all paths by which the user-controlled title reaches the command.
Explanation
Correct Answer
B:Trace the workflow's event context, checked-out ref, executed commands, token permission and available secrets. Privileged workflow triggers require strict separation from untrusted pull request code and controlled checkout targets. Retain only safe metadata operations in the privileged workflow and move fork-code tests into isolated low-privilege jobs.
Incorrect Answers
A:Inspect triggers, concurrency group expressions, active run histories and the deployment service's rollback behavior. That check would not establish the decisive facts for this condition: An organization uses pull_request_target to label contributor pull requests but also checks out the contributor's head commit and executes its scripts using a privileged token. Trace the workflow's event context, checked-out ref, executed commands, token permission and available secrets.
C:Check the secret's selected-repository visibility settings and every workflow currently referencing it. That check would not establish the decisive facts for this condition: An organization uses pull_request_target to label contributor pull requests but also checks out the contributor's head commit and executes its scripts using a privileged token. Trace the workflow's event context, checked-out ref, executed commands, token permission and available secrets.
D:Inspect the workflow YAML expression, job shell and all paths by which the user-controlled title reaches the command. That check would not establish the decisive facts for this condition: An organization uses pull_request_target to label contributor pull requests but also checks out the contributor's head commit and executes its scripts using a privileged token. Trace the workflow's event context, checked-out ref, executed commands, token permission and available secrets.
Question 463
GitHub Enterprise administration scenario — Guard pull_request_target workflows. In an enterprise development environment: An organization uses pull_request_target to label contributor pull requests but also checks out the contributor's head commit and executes its scripts using a privileged token. The enterprise administrator needs a least-privilege corrective change with accountable approval and rollback. Which action BEST resolves the reported GitHub configuration or governance problem? Choose ONE best answer.
- Retain only safe metadata operations in the privileged workflow and move fork-code tests into isolated low-privilege jobs.
- Configure a supported allow policy with reviewed first-party or approved action exceptions and test representative pipelines.
- Correct the supported selector or provision an appropriately labeled authorized runner with approval.
- Retire and revoke the old cloud key, remove stale Actions secrets and retain a supported rollback plan.
Explanation
Correct Answer
A:Retain only safe metadata operations in the privileged workflow and move fork-code tests into isolated low-privilege jobs. Trace the workflow's event context, checked-out ref, executed commands, token permission and available secrets. Labels are applied correctly while untrusted PR scripts cannot run with the privileged workflow's token.
Incorrect Answers
B:Configure a supported allow policy with reviewed first-party or approved action exceptions and test representative pipelines. That change would leave the reported problem unresolved: An organization uses pull_request_target to label contributor pull requests but also checks out the contributor's head commit and executes its scripts using a privileged token. Retain only safe metadata operations in the privileged workflow and move fork-code tests into isolated low-privilege jobs.
C:Correct the supported selector or provision an appropriately labeled authorized runner with approval. That change would leave the reported problem unresolved: An organization uses pull_request_target to label contributor pull requests but also checks out the contributor's head commit and executes its scripts using a privileged token. Retain only safe metadata operations in the privileged workflow and move fork-code tests into isolated low-privilege jobs.
D:Retire and revoke the old cloud key, remove stale Actions secrets and retain a supported rollback plan. That change would leave the reported problem unresolved: An organization uses pull_request_target to label contributor pull requests but also checks out the contributor's head commit and executes its scripts using a privileged token. Retain only safe metadata operations in the privileged workflow and move fork-code tests into isolated low-privilege jobs.
Question 464
GitHub Enterprise administration scenario — Guard pull_request_target workflows. In an enterprise development environment: An organization uses pull_request_target to label contributor pull requests but also checks out the contributor's head commit and executes its scripts using a privileged token. The change reviewer separates a justified investigation from a merely plausible fix. Select EXACTLY TWO: the decisive diagnostic evidence required BEFORE change and the independent successful result that must be verified AFTER change.
- Inspect vault roles, supported federation mechanisms, workflow permissions, secret consumers and review gates.
- Compare copies of deployment steps, trigger contexts, secrets passed and existing shared workflow permissions.
- Labels are applied correctly while untrusted PR scripts cannot run with the privileged workflow's token.
- Runner group access matches the approved organization list and the change actor is recorded for investigation.
- Trace the workflow's event context, checked-out ref, executed commands, token permission and available secrets.
Explanation
Correct Answers
C:Labels are applied correctly while untrusted PR scripts cannot run with the privileged workflow's token. Trace the workflow's event context, checked-out ref, executed commands, token permission and available secrets. Privileged workflow triggers require strict separation from untrusted pull request code and controlled checkout targets.
E:Trace the workflow's event context, checked-out ref, executed commands, token permission and available secrets. Labels are applied correctly while untrusted PR scripts cannot run with the privileged workflow's token. Retain only safe metadata operations in the privileged workflow and move fork-code tests into isolated low-privilege jobs.
Incorrect Answers
A:Inspect vault roles, supported federation mechanisms, workflow permissions, secret consumers and review gates. It would not provide the evidence needed for the paired diagnosis and follow-up: An organization uses pull_request_target to label contributor pull requests but also checks out the contributor's head commit and executes its scripts using a privileged token. Trace the workflow's event context, checked-out ref, executed commands, token permission and available secrets. Labels are applied correctly while untrusted PR scripts cannot run with the privileged workflow's token.
B:Compare copies of deployment steps, trigger contexts, secrets passed and existing shared workflow permissions. It would not provide the evidence needed for the paired diagnosis and follow-up: An organization uses pull_request_target to label contributor pull requests but also checks out the contributor's head commit and executes its scripts using a privileged token. Trace the workflow's event context, checked-out ref, executed commands, token permission and available secrets. Labels are applied correctly while untrusted PR scripts cannot run with the privileged workflow's token.
D:Runner group access matches the approved organization list and the change actor is recorded for investigation. It would not verify whether the proposed change works: An organization uses pull_request_target to label contributor pull requests but also checks out the contributor's head commit and executes its scripts using a privileged token. Labels are applied correctly while untrusted PR scripts cannot run with the privileged workflow's token. Retain only safe metadata operations in the privileged workflow and move fork-code tests into isolated low-privilege jobs.
Question 465
GitHub Enterprise administration scenario — Guard pull_request_target workflows. In an enterprise development environment: An organization uses pull_request_target to label contributor pull requests but also checks out the contributor's head commit and executes its scripts using a privileged token. A controlled enterprise configuration review requires a coherent rationale, approved change and confirmed outcome. Select EXACTLY THREE: the governing GitHub administration principle, the proportionate authorized intervention AND the independently observable outcome for this scenario.
- Retain only safe metadata operations in the privileged workflow and move fork-code tests into isolated low-privilege jobs.
- Labels are applied correctly while untrusted PR scripts cannot run with the privileged workflow's token.
- The payment release can use its runner pool while an unrelated repository cannot schedule jobs there.
- Reusable workflow secret passing should be explicit and consistent with the callee's trust boundary and job purpose.
- Isolate privileged caches or rebuild trusted dependencies for release paths using reviewed actions and keys.
- Privileged workflow triggers require strict separation from untrusted pull request code and controlled checkout targets.
Explanation
Correct Answers
A:Retain only safe metadata operations in the privileged workflow and move fork-code tests into isolated low-privilege jobs. Privileged workflow triggers require strict separation from untrusted pull request code and controlled checkout targets. Labels are applied correctly while untrusted PR scripts cannot run with the privileged workflow's token.
B:Labels are applied correctly while untrusted PR scripts cannot run with the privileged workflow's token. Retain only safe metadata operations in the privileged workflow and move fork-code tests into isolated low-privilege jobs. Privileged workflow triggers require strict separation from untrusted pull request code and controlled checkout targets.
F:Privileged workflow triggers require strict separation from untrusted pull request code and controlled checkout targets. Retain only safe metadata operations in the privileged workflow and move fork-code tests into isolated low-privilege jobs. Labels are applied correctly while untrusted PR scripts cannot run with the privileged workflow's token.
Incorrect Answers
C:The payment release can use its runner pool while an unrelated repository cannot schedule jobs there. It would not independently demonstrate that the control works: An organization uses pull_request_target to label contributor pull requests but also checks out the contributor's head commit and executes its scripts using a privileged token. Labels are applied correctly while untrusted PR scripts cannot run with the privileged workflow's token. Retain only safe metadata operations in the privileged workflow and move fork-code tests into isolated low-privilege jobs.
D:Reusable workflow secret passing should be explicit and consistent with the callee's trust boundary and job purpose. It is not the rule that supports the proposed change and acceptance test: An organization uses pull_request_target to label contributor pull requests but also checks out the contributor's head commit and executes its scripts using a privileged token. Privileged workflow triggers require strict separation from untrusted pull request code and controlled checkout targets. Retain only safe metadata operations in the privileged workflow and move fork-code tests into isolated low-privilege jobs.
E:Isolate privileged caches or rebuild trusted dependencies for release paths using reviewed actions and keys. It does not implement the governing rule for this approval: An organization uses pull_request_target to label contributor pull requests but also checks out the contributor's head commit and executes its scripts using a privileged token. Retain only safe metadata operations in the privileged workflow and move fork-code tests into isolated low-privilege jobs. Labels are applied correctly while untrusted PR scripts cannot run with the privileged workflow's token.
Question 466
GitHub Enterprise administration scenario — Prevent workflow expression injection. In an enterprise development environment: A workflow embeds the pull request title directly into a shell command and a tester demonstrates that quotes inside the title change the command meaning. The administrator must identify the controlling access, governance or platform principle rather than an unrelated configuration fix. Which principle BEST addresses this condition? Choose ONE best answer.
- Untrusted event data should not be interpolated into executable shell syntax without isolation or strict handling.
- OIDC federation can replace static cloud credentials with short-lived, policy-constrained tokens for supported providers.
- Sensitive workflow values should not be logged even when GitHub masking reduces visibility for recognized secrets.
- Runner label and group selection must match actual eligible connected runner inventory for a job to schedule.
Explanation
Correct Answer
A:Untrusted event data should not be interpolated into executable shell syntax without isolation or strict handling. Inspect the workflow YAML expression, job shell and all paths by which the user-controlled title reaches the command. Move external values through appropriately quoted environment variables or vetted actions and remove unsafe command interpolation.
Incorrect Answers
B:OIDC federation can replace static cloud credentials with short-lived, policy-constrained tokens for supported providers. It does not govern the condition described: A workflow embeds the pull request title directly into a shell command and a tester demonstrates that quotes inside the title change the command meaning. Untrusted event data should not be interpolated into executable shell syntax without isolation or strict handling.
C:Sensitive workflow values should not be logged even when GitHub masking reduces visibility for recognized secrets. It does not govern the condition described: A workflow embeds the pull request title directly into a shell command and a tester demonstrates that quotes inside the title change the command meaning. Untrusted event data should not be interpolated into executable shell syntax without isolation or strict handling.
D:Runner label and group selection must match actual eligible connected runner inventory for a job to schedule. It does not govern the condition described: A workflow embeds the pull request title directly into a shell command and a tester demonstrates that quotes inside the title change the command meaning. Untrusted event data should not be interpolated into executable shell syntax without isolation or strict handling.
Question 467
GitHub Enterprise administration scenario — Prevent workflow expression injection. In an enterprise development environment: A workflow embeds the pull request title directly into a shell command and a tester demonstrates that quotes inside the title change the command meaning. Before changing enterprise policies, permissions or workflows, which diagnostic check BEST establishes the decisive fact? Choose ONE best answer.
- Review environment branch restrictions, required reviewers, workflow triggers and production secret placement.
- Inspect runner reuse, workspace cleanup, image provenance and job isolation requirements.
- Compare hosted runner usage, workflow matrix dimensions, cache efficiency and configured enterprise budgets.
- Inspect the workflow YAML expression, job shell and all paths by which the user-controlled title reaches the command.
Explanation
Correct Answer
D:Inspect the workflow YAML expression, job shell and all paths by which the user-controlled title reaches the command. Untrusted event data should not be interpolated into executable shell syntax without isolation or strict handling. Move external values through appropriately quoted environment variables or vetted actions and remove unsafe command interpolation.
Incorrect Answers
A:Review environment branch restrictions, required reviewers, workflow triggers and production secret placement. That check would not establish the decisive facts for this condition: A workflow embeds the pull request title directly into a shell command and a tester demonstrates that quotes inside the title change the command meaning. Inspect the workflow YAML expression, job shell and all paths by which the user-controlled title reaches the command.
B:Inspect runner reuse, workspace cleanup, image provenance and job isolation requirements. That check would not establish the decisive facts for this condition: A workflow embeds the pull request title directly into a shell command and a tester demonstrates that quotes inside the title change the command meaning. Inspect the workflow YAML expression, job shell and all paths by which the user-controlled title reaches the command.
C:Compare hosted runner usage, workflow matrix dimensions, cache efficiency and configured enterprise budgets. That check would not establish the decisive facts for this condition: A workflow embeds the pull request title directly into a shell command and a tester demonstrates that quotes inside the title change the command meaning. Inspect the workflow YAML expression, job shell and all paths by which the user-controlled title reaches the command.
Question 468
GitHub Enterprise administration scenario — Prevent workflow expression injection. In an enterprise development environment: A workflow embeds the pull request title directly into a shell command and a tester demonstrates that quotes inside the title change the command meaning. The enterprise administrator needs a least-privilege corrective change with accountable approval and rollback. Which action BEST resolves the reported GitHub configuration or governance problem? Choose ONE best answer.
- Configure a supported allow policy with reviewed first-party or approved action exceptions and test representative pipelines.
- Separate untrusted validation from privileged deployment and remove secrets from fork-triggered execution contexts.
- Move external values through appropriately quoted environment variables or vetted actions and remove unsafe command interpolation.
- Revert the unapproved expansion and add ownership reviews or automated alerts for sensitive runner policy changes.
Explanation
Correct Answer
C:Move external values through appropriately quoted environment variables or vetted actions and remove unsafe command interpolation. Inspect the workflow YAML expression, job shell and all paths by which the user-controlled title reaches the command. A malicious test title is processed as inert data and cannot trigger an unintended shell command.
Incorrect Answers
A:Configure a supported allow policy with reviewed first-party or approved action exceptions and test representative pipelines. That change would leave the reported problem unresolved: A workflow embeds the pull request title directly into a shell command and a tester demonstrates that quotes inside the title change the command meaning. Move external values through appropriately quoted environment variables or vetted actions and remove unsafe command interpolation.
B:Separate untrusted validation from privileged deployment and remove secrets from fork-triggered execution contexts. That change would leave the reported problem unresolved: A workflow embeds the pull request title directly into a shell command and a tester demonstrates that quotes inside the title change the command meaning. Move external values through appropriately quoted environment variables or vetted actions and remove unsafe command interpolation.
D:Revert the unapproved expansion and add ownership reviews or automated alerts for sensitive runner policy changes. That change would leave the reported problem unresolved: A workflow embeds the pull request title directly into a shell command and a tester demonstrates that quotes inside the title change the command meaning. Move external values through appropriately quoted environment variables or vetted actions and remove unsafe command interpolation.
Question 469
GitHub Enterprise administration scenario — Prevent workflow expression injection. In an enterprise development environment: A workflow embeds the pull request title directly into a shell command and a tester demonstrates that quotes inside the title change the command meaning. The change reviewer separates a justified investigation from a merely plausible fix. Select EXACTLY TWO: the decisive diagnostic evidence required BEFORE change and the independent successful result that must be verified AFTER change.
- Monthly minutes fall to planned limits while critical build and security checks continue to run.
- A malicious test title is processed as inert data and cannot trigger an unintended shell command.
- Inspect the workflow YAML expression, job shell and all paths by which the user-controlled title reaches the command.
- Trace the workflow's event context, checked-out ref, executed commands, token permission and available secrets.
- Inspect the action repository provenance, requested workflow permissions, update history and verified commit reference.
Explanation
Correct Answers
B:A malicious test title is processed as inert data and cannot trigger an unintended shell command. Inspect the workflow YAML expression, job shell and all paths by which the user-controlled title reaches the command. Untrusted event data should not be interpolated into executable shell syntax without isolation or strict handling.
C:Inspect the workflow YAML expression, job shell and all paths by which the user-controlled title reaches the command. A malicious test title is processed as inert data and cannot trigger an unintended shell command. Move external values through appropriately quoted environment variables or vetted actions and remove unsafe command interpolation.
Incorrect Answers
A:Monthly minutes fall to planned limits while critical build and security checks continue to run. It would not verify whether the proposed change works: A workflow embeds the pull request title directly into a shell command and a tester demonstrates that quotes inside the title change the command meaning. A malicious test title is processed as inert data and cannot trigger an unintended shell command. Move external values through appropriately quoted environment variables or vetted actions and remove unsafe command interpolation.
D:Trace the workflow's event context, checked-out ref, executed commands, token permission and available secrets. It would not provide the evidence needed for the paired diagnosis and follow-up: A workflow embeds the pull request title directly into a shell command and a tester demonstrates that quotes inside the title change the command meaning. Inspect the workflow YAML expression, job shell and all paths by which the user-controlled title reaches the command. A malicious test title is processed as inert data and cannot trigger an unintended shell command.
E:Inspect the action repository provenance, requested workflow permissions, update history and verified commit reference. It would not provide the evidence needed for the paired diagnosis and follow-up: A workflow embeds the pull request title directly into a shell command and a tester demonstrates that quotes inside the title change the command meaning. Inspect the workflow YAML expression, job shell and all paths by which the user-controlled title reaches the command. A malicious test title is processed as inert data and cannot trigger an unintended shell command.
Question 470
GitHub Enterprise administration scenario — Prevent workflow expression injection. In an enterprise development environment: A workflow embeds the pull request title directly into a shell command and a tester demonstrates that quotes inside the title change the command meaning. A controlled enterprise configuration review requires a coherent rationale, approved change and confirmed outcome. Select EXACTLY THREE: the governing GitHub administration principle, the proportionate authorized intervention AND the independently observable outcome for this scenario.
- A fork pull request cannot access internal runner resources while its safe build tests still execute.
- Publish a versioned approved reusable workflow and migrate caller repositories through reviewed pull requests.
- Move external values through appropriately quoted environment variables or vetted actions and remove unsafe command interpolation.
- Untrusted event data should not be interpolated into executable shell syntax without isolation or strict handling.
- A malicious test title is processed as inert data and cannot trigger an unintended shell command.
- Privileged workflow triggers require strict separation from untrusted pull request code and controlled checkout targets.
Explanation
Correct Answers
C:Move external values through appropriately quoted environment variables or vetted actions and remove unsafe command interpolation. Untrusted event data should not be interpolated into executable shell syntax without isolation or strict handling. A malicious test title is processed as inert data and cannot trigger an unintended shell command.
D:Untrusted event data should not be interpolated into executable shell syntax without isolation or strict handling. Move external values through appropriately quoted environment variables or vetted actions and remove unsafe command interpolation. A malicious test title is processed as inert data and cannot trigger an unintended shell command.
E:A malicious test title is processed as inert data and cannot trigger an unintended shell command. Move external values through appropriately quoted environment variables or vetted actions and remove unsafe command interpolation. Untrusted event data should not be interpolated into executable shell syntax without isolation or strict handling.
Incorrect Answers
A:A fork pull request cannot access internal runner resources while its safe build tests still execute. It would not independently demonstrate that the control works: A workflow embeds the pull request title directly into a shell command and a tester demonstrates that quotes inside the title change the command meaning. A malicious test title is processed as inert data and cannot trigger an unintended shell command. Move external values through appropriately quoted environment variables or vetted actions and remove unsafe command interpolation.
B:Publish a versioned approved reusable workflow and migrate caller repositories through reviewed pull requests. It does not implement the governing rule for this approval: A workflow embeds the pull request title directly into a shell command and a tester demonstrates that quotes inside the title change the command meaning. Move external values through appropriately quoted environment variables or vetted actions and remove unsafe command interpolation. A malicious test title is processed as inert data and cannot trigger an unintended shell command.
F:Privileged workflow triggers require strict separation from untrusted pull request code and controlled checkout targets. It is not the rule that supports the proposed change and acceptance test: A workflow embeds the pull request title directly into a shell command and a tester demonstrates that quotes inside the title change the command meaning. Untrusted event data should not be interpolated into executable shell syntax without isolation or strict handling. Move external values through appropriately quoted environment variables or vetted actions and remove unsafe command interpolation.