![]() I am writing this post as much for myself as my two readers, as a means of increasing my familiarity with the Git/Bash ecosystem (what better way than to explain it to someone else, right?), and so that I will have a reference to my own best thinking on the subject, relevant links, and such. Some are better than others, and it is great to get information and opinions from a variety of sources. The web is chock full of tutorials on using git and Github. In many cases, better than I am about to cover it. Hasn’t All of this been covered somewhere else? Once I graduated to using version control for my code, there was no turning back. IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,įITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT.I am a late-comer to version control in general, and, having grown up teaching myself programming in the Windows/Visual Studio/C# realm, It took the growing prominence of Github to draw my attention to what is currently the most visible Distributed Version Control System (and “social coding” site) in the developer universe. 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. Use the manual installation to build from source, useful if you intend to help make Gitify better. To fix this, you'll need to set your global minimum stability with the following command: composer global config minimum-stability alpha (Composer defaults to stable, and we want an unstable version!) Get an error message pertaining to your minimum-stability setting. When installing an alpha/dev version, if you haven't modified your global composer config before, it's possible you'll In that case you'll need to use vendor/bin/gitify as the command. To update, use composer global update modmore/gitify.Īlternatively, you can install Gitify local to a project with composer require modmore/gitify:^2. in the ~/.bash_profile or ~/.zshrc file on Mac/Linux). If that does not make gitify available on your path, add the output of composer global config bin-dir -absolute to your path (i.e. Installation composer global require modmore/gitify:^2
0 Comments
Leave a Reply. |