Changes to map repos on GitHub
-
Just a heads-up for all map makers...
Some build-related files that are no longer used (.travis.yml and build.gradle) were removed from almost every map repo in the triplea-maps organization on GitHub (see https://github.com/triplea-maps/Project/issues/89 for details). If you have any pending changes you have not yet pushed to your repo on GitHub, you will have to resync with the remote first (i.e.
git pull). The files that were removed have nothing to do with the map definitions themselves, and so you shouldn't see any merge conflicts when you resync.Please leave a comment at the above issue if you notice any problems.
-
@ssoloff Was that ancient Assyrian? Are any of us mere mortals supposed to understand any part of that?
"A joyous heart sours with the burden of expectation"
Hepster -
@ssoloff So, if I usually just drag-and-drop upload stuff to GitHub, then I don't have to care about any of this, am I correct?
"For the world is changing: I feel it in the water, I feel it in the earth, and I smell it in the air."
-
@hepps It's called "Githubese" ... similar to "Chinese"
-
@Hepps Sorry, I assumed you map makers all had the official-issue secret decoder ring we hand out over at GitHub.
@alkexr I don't think you'll have any problems because you'll only be DnD'ing a file which was not touched by these changes, and the GitHub web UI should be smart enough to figure that out. If I'm wrong, just open an issue on GitHub, and we'll straighten everything out again.
Hello! It looks like you're interested in this conversation, but you don't have an account yet.
Getting fed up of having to scroll through the same posts each visit? When you register for an account, you'll always come back to exactly where you were before, and choose to be notified of new replies (either via email, or push notification). You'll also be able to save bookmarks and upvote posts to show your appreciation to other community members.
With your input, this post could be even better 💗
Register Login