Fix unresolved merge conflict markers in DevUtilities - #439
Merged
shamilahmdt merged 1 commit intoAug 3, 2026
Conversation
|
@farzan2004 is attempting to deploy a commit to the shamilahmdt's projects Team on Vercel. A member of the Team first needs to authorize it. |
👋 Hello, @farzan2004!Thank you for your contribution to DevTasks. The maintainer has been notified and will review your pull request shortly. If any changes are needed, we will let you know in the comments below. |
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
📝 Description
Fix unresolved merge conflict markers in DevUtilities.
Summary
This PR removes unresolved Git merge conflict markers that were accidentally committed into
DevUtilities.jsx.These markers caused the project build to fail after the previous merge.
Changes
DevUtilities.jsxnpm run build)