You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
hollowaykeanho opened this issue
Sep 20, 2023
· 4 comments
Assignees
Labels
BugCase is about a glitch.CriticalRed alert. High attention needed.ReleasedImplementation got released and shipped.SecurityCase is a security vulnerability matter.
Apparently, if the releases directory is missing or malformed, Release job will hard reset the root repository to its first commit and official nuke the project. This is not desirable and safety check must me added here to prevent this from happening again.
Expected Behavior
Safety check is added to GIT::hard_reset_to_init function to cross-check its root against the root repository before actually performing the reset.
Current Behavior
No safety check is added.
Steps to Reproduce [COMPULSORY]
Execute everything.
At ./ci release stage, observe that it shall erase the project and attempting to push to remote.
Associated Data Files
No response
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Labels
BugCase is about a glitch.CriticalRed alert. High attention needed.ReleasedImplementation got released and shipped.SecurityCase is a security vulnerability matter.
Description
Apparently, if the releases directory is missing or malformed, Release job will hard reset the root repository to its first commit and official nuke the project. This is not desirable and safety check must me added here to prevent this from happening again.
Expected Behavior
Safety check is added to
GIT::hard_reset_to_init
function to cross-check its root against the root repository before actually performing the reset.Current Behavior
No safety check is added.
Steps to Reproduce [COMPULSORY]
./ci release
stage, observe that it shall erase the project and attempting to push to remote.Associated Data Files
No response
The text was updated successfully, but these errors were encountered: