Ensure the MAYHEM_PROJECT envvar is initialized consistently.

[ethan42]

The MAYHEM_PROJECT name may differ from the repository name - and this is why the project/owner fields are inputs to this flow; the code before was not allowing for that differentiation.

[github-actions]

Mayhem Automated Code Testing Report

❗ 1 Defects Found

CWE Severity	Defect	Description
7.1	Improper Input Validation	The product receives input or data, but it does not validate or incorrectly validates that the input has the properties that are required to process the data safely and correctly.

---

Testing details found at https://app.mayhem.security/forallsecure/mcode-action/mayhemit/37

[github-advanced-security]

You are seeing this message because GitHub Code Scanning has recently been set up for this repository, or this pull request contains the workflow file for the Code Scanning tool.

What Enabling Code Scanning Means:

• The 'Security' tab will display more code scanning analysis results (e.g., for the default branch).
• Depending on your configuration and choice of analysis tool, future pull requests will be annotated with code scanning analysis results.
• You will be able to see the analysis results for the pull request's branch on this overview once the scans have completed and the checks have passed.

For more information about GitHub Code Scanning, check out the documentation.

[dbrumley]

It seems the new code does not use repo at all; is that intentional? I'm not sure what the repo field even is.

[ethan42]

it is github_workspace/github_project. there was an implied assumption that MAYHEM_PROJECT must be the same as the github combo.