Repository navigation
Fix Availability PHP parse error from committed conflict markers - #80
Merged
Merged
Conversation
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
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.
Problem
Commit 7a21ce1 committed unresolved stash-conflict markers in six Availability files.
index.phpbegins with<<<<<<< Updated upstreamon line 2, causing the exact PHP parse error reported on the live site. API PHP, JavaScript, README, changelog and project JSON also contain conflict markers.Repair
Validation
Deployment
Merge and allow Hostinger to sync the repaired source. Runtime event data is not modified. The live site repair has not yet been deployed/verified.