| -- | |
| -- This query delelets all customers and orders from your | |
| -- Magento 1.* install. Handy, if you have a bloated | |
| -- Magento database and you need to do a bit | |
| -- of cleaning up for use on a local machine. | |
| -- | |
| -- Replace PREFIX_ with your current Magento table prefix. | |
| -- | |
| -- USE AT OWN RISK. ALWAY BACKUP YOUR DATABASE FIRST. | |
| -- |
| # | |
| # Basic process for merging two Git repositories while retaining commit history. | |
| # - This seems to work pretty well for migrations to Pantheon | |
| # | |
| # Clone the repository that will be the final origin | |
| git clone <repository_uri_1> <local_dir> | |
| cd <local_dir> | |
| # Add the second repository as a remote |
| # --------------------------------------------------------------------------- | |
| # | |
| # Description: This file holds all my BASH configurations and aliases | |
| # | |
| # Sections: | |
| # 1. Environment Configuration | |
| # 2. Make Terminal Better (remapping defaults and adding functionality) | |
| # 3. File and Folder Management | |
| # 4. Searching | |
| # 5. Process Management |
This Gist is a collection of configuration files that can be used to easily setup a Homebrew-based LEMP stack on Mac OS X.
Files in this repository are numbered and named for ordering purposes only. At the top of each file is a section of metadata that denote what component the file belongs to and the default name & location of the file. Feel free to implement it however you want.
Note: some configuration files have hard-coded paths to my user directory -- fix it for your setup
| Make sure your in develop | |
| git flow hotfix start [Release Number] | |
| git add -A | |
| git commit *** Commit the change and give description | |
| git flow hotfix finish [Release Number] *** Be sure to label Tags | |
| git push *** When you push it will push to both branches that were setup in git flow init | |
| git push --tags *** These will appear in the Releases link on GitHub |
This is the process I have found to be very helpful when migrating projects from their SVN repository over to Git. When migrating from one version control system to another it's important to retain as much information about the development history as possible (i.e., commit messages, tags, branches, etc.) and avoid the easy and tempting method of just downloading the project from a server and throw it into the new version control (you should only consider that if the project has never been in a version control system before).
Key concepts: