-
Notifications
You must be signed in to change notification settings - Fork 514
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Test #9469
Closed
+145
−99
Closed
Test #9469
Changes from 4 commits
Commits
Show all changes
10 commits
Select commit
Hold shift + click to select a range
42ae69b
testing yaml file
manmeetnagii 50f1b44
testing yaml file again
manmeetnagii 64d1d02
back to original yaml
manmeetnagii 7a25bca
testing yaml
manmeetnagii 2a0160e
testing assrtList
manmeetnagii 28cc4da
asset mb change
manmeetnagii beff1c7
set id as type exportitem
manmeetnagii eff81fb
Checking assetList
manmeetnagii 27a9689
testing assetList.tsx
manmeetnagii e7d6c2e
change color
manmeetnagii File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
💡 Codebase verification
Repository condition change introduces security risks
The verification confirms critical security concerns:
The workflow has
write-all
permissions and handles sensitive operations including:All other security-critical workflows (CodeQL, OSSAR, deployments) are correctly restricted to 'ohcnetwork/care_fe', while this is the only workflow changed to run on a personal fork.
The workflow already has proper fork handling through
steps.pr_origin.outputs.is_forked
conditions, making the repository check redundant and potentially harmful.Recommendation:
🔗 Analysis chain
SECURITY RISK: Workflow configured for personal fork instead of main repository
This change presents several critical concerns:
Security:
write-all
permissions and runs with sensitive secretsCI/CD Pipeline:
Revert this change to maintain security and ensure proper CI/CD pipeline execution:
Let's verify the repository settings and permissions:
Let's examine the workflow file contents and any other repository conditions to better understand the security implications and verify if this is indeed a critical issue.
🏁 Scripts executed
The following scripts were executed for the analysis:
Script:
Length of output: 943
Script:
Length of output: 6137