-
Notifications
You must be signed in to change notification settings - Fork 3
Official Zoho CRM Submission - DannyDrills #5
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
base: master
Are you sure you want to change the base?
Changes from all commits
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -1,3 +1,8 @@ | ||
| <<<<<<< HEAD | ||
| node_modules/ | ||
| dist/ | ||
| .env | ||
| ======= | ||
|
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Merge conflict markers left in gitignore fileHigh Severity Unresolved git merge conflict markers ( Additional Locations (1) |
||
| # Dependencies | ||
| node_modules/ | ||
| npm-debug.log* | ||
|
|
@@ -96,3 +101,4 @@ template/.lua/ | |
| *.lua.skill.toml | ||
| lua.skill.toml | ||
| *.prompt.* | ||
| >>>>>>> final-submission/master | ||


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.
Unresolved merge conflict markers committed in gitignore
High Severity
The
.gitignorefile contains unresolved git merge conflict markers (<<<<<<< HEAD,=======,>>>>>>> final-submission/master). This means the file was never properly resolved after a merge and the conflict markers are treated as literal text. This effectively breaks the gitignore rules above the=======marker (the simplified block), since git interprets the marker lines as file patterns rather than directives.Additional Locations (1)
.gitignore#L103-L104