Merge conflict after update to 2.19

sdetweil

@DarrenHill rule 1. NEVER change the mm supplied source.

you can do all the config thru the config.js.

DarrenHill

@sdetweil Yes, I’m not quite sure what the weatherforecast.js change was, but that’s blown away now. As you say, the new module is fine with a little tweaking via custom.css.

It was the package.json file that screwed things up, and that I know I have never touched and have no idea what it was and why it got out of sync.

Anyway I learned a bit of stuff about GitHub and stashing, so that’s a bonus and we’re up and running again fine (after swapping out the depreciated weather modules too).

sdetweil

@DarrenHill
the

git diff  x

command
will show you the changes

x is an optional file name.
if not supplied, it will show all changes to all changes files

git status will show you if any files are changed

DarrenHill

@sdetweil Good to know.

git status got me out of it, as I think things got out of sync rather than really needing merging or proper tracking (if subsequent research on what package.json actually means and does).

But useful to know how to actually see the differences for future reference. I really need to get more skilled-up on GitHub, but it always defeats me as I’m only an occasional hobby programmer for personal usage rather than for sharing/collaboration.

sdetweil

also

git checkout filename

will restore a file to it’s repo contents.

sdetweil

@DarrenHill git is the thing

gitHUB is just server for holding code, and accepting changes (pull requests) from others