Skip to content

Conversation

@mlawsonca
Copy link
Collaborator

Steps for the author:

  • Commit message follows the guidelines.
  • Appropriate Features or Test-tag pragmas were used.
  • Appropriate Functional Test Stages were run.
  • At least two positive code reviews including at least one code owner from each category referenced in the PR.
  • Testing is complete. If necessary, forced-landing label added and a reason added in a comment.

After all prior steps are complete:

  • Gatekeeper requested (daos-gatekeeper added as a reviewer).

Signed-off-by: mlawsonca <mlawsonca@users.noreply.github.com>
@mlawsonca mlawsonca requested a review from a team as a code owner March 5, 2025 03:45
@github-actions
Copy link

github-actions bot commented Mar 5, 2025

Errors are component not formatted correctly,Ticket number prefix incorrect,PR title is malformatted. See https://daosio.atlassian.net/wiki/spaces/DC/pages/11133911069/Commit+Comments,Unable to load ticket data
https://daosio.atlassian.net/browse/Create

Skip-build: true

Signed-off-by: mlawsonca <mlawsonca@users.noreply.github.com>
@@ -0,0 +1,14 @@
name: Check variable value

Check failure

Code scanning / Scorecard

Token-Permissions High

score is 0: no topLevel permission defined
Remediation tip: Visit https://app.stepsecurity.io/secureworkflow.
Tick the 'Restrict permissions for GITHUB_TOKEN'
Untick other options
NOTE: If you want to resolve multiple issues at once, you can visit https://app.stepsecurity.io/securerepo instead.
Click Remediation section below for further remediation help
@mlawsonca mlawsonca closed this Jun 7, 2025
@mlawsonca mlawsonca deleted the mlawsonca/check_variable_workflow branch June 7, 2025 22:21
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Development

Successfully merging this pull request may close these issues.

2 participants