IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,įITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR The above copyright notice and this permission notice shall be included in allĬopies or substantial portions of the Software. To use, copy, modify, merge, publish, distribute, sublicense, and/or sellĬopies of the Software, and to permit persons to whom the Software isįurnished to do so, subject to the following conditions: In the Software without restriction, including without limitation the rights Of this software and associated documentation files (the "Software"), to deal Permission is hereby granted, free of charge, to any person obtaining a copy LicenseĬopyright (c) 2014-2015 modmore | More for MODX As we are before v1 right now, expect breaking changes and refactorings before the API stabilises.įor changes, please see the commit log or the Changelog. Please feel free to contribute to the wiki by editing existing pages, or adding new pages with extra information not covered elsewhere yet. DocumentationĬheck the modmore Gitify documentation! It contains information about the available commands and the way you would go about setting up a suitable workflow. Please see the Installation documentation for more details. Gitify has changed to gitify and is now in a /bin subdirectory.The minimum PHP version has been increased to 7.2.5.Make sure you've upgraded to the latest version. Gitify v2 is now compatible with Gitify Watch v2.To upgrade simply to use Gitify, it's recommended to remove the v1 git-based installation completely, and instead install Gitify globally with Composer as described in the installation section below.This may be in your ~/.bash_profile or ~/.zshrc file. Update your $PATH to point to the bin directory.Install updated dependencies ( composer install).Bring it up to date with the master branch ( git fetch origin & git reset -hard origin/master, or git fetch upstream & git reset -hard upstream/master).To upgrade with the intention of contributing to Gitify, you can keep your exiting git installation.The data file structure is unchanged, so you can safely update to v2. Gitify v2 brings updated dependencies, additional functionality, and easier installation/updates via Composer. The project configuration, which determines what data is written to file and build to the database, is stored in a. The migxConfig should be the last item of the MIGX objects. MIGX If you’re using MIGX configs and the Gitify files for the configs changes after each build and extract command of Gitify, you might need to pay attention to your order of the MIGX objects in your. These files follow a certain human and machine friendly format, built from a block of YAML, followed by a separator, and then the main content (if there's a specific content field) below that. See the Windows or Mac installation documentation. To do this, it creates a representation of MODX objects in files. These would most definitely be invisible to the local system, so they'd never really be identified (remote repo is more like a 'blessed' one, is rarely cross checked).The goal of Gitify is to provide a two-way sync of data typically stored in the MODX database, making it versionable with Git. My guess is that maybe an oddly configured git client was used to stage these files sometime before where staging occurred with case sensitivity, thus introducing such paths. Wood also narrates a similar journey, along with suggesting a tool he made himself to fix such issues. However, the git index isn't (or at least wasn't whenever this happened, as it can be made insensitive) case insensitive, so it maintains the path as different ones. That's why it is there where it should be on the local file system. Since Windows File System is case insensitive, it treats both the same. Turned out, that the file did exist on GitHub, but the entire path to it was somehow made case sensitive, and so it was showing under /foo/bar/baz rather than /Foo/Bar/Baz, where it was supposed to be. A few minutes later, he came back in shock, saying that the file wasn't there at all on GitHub where it should be! This was extremely surprising, so had to investigate. I lazily bounced it back by suggesting to browse the tree at GitHub itself before a certain commit, and it'll be easier as well to search directly off the browser. Since the file itself was huge and was going through a massive re-work, I was committing moderately whenever I had worked on a particular module, so as to keep everything stable.Ī colleague of mine hit up a request to dig up some pieces of code in the same file which were there before the rework. I was working on Windows and using Git Bash as my client, with a remote repository hosted on GitHub. Lately, I came across a situation when I was working on a file which had to undergo extremely major changes.
0 Comments
Leave a Reply. |