The engineers at GitHub have documented this technique.įrom within the Drupal root of your site: If you find that you're running into issues with commits that reference sites/default/files, use the filter-branch command to rewrite those references out of your repository. Why were pushes denied because of changes in sites/default/files? When Git mode is enabled, you can interact with your code via Git. When you switch to On Server Development (SFTP), you cannot interact with your code via Git. Not simultaneously, but it's easy to switch back and forth. How do I import a site with existing Git history?įor detailed instructions, see Manually Migrate Sites to Pantheon. A best practice is to include a link to the issue/comment where the patch came from in your commit message.ĭ also has instructions if you're looking to give back by creating patches for Drupal. You will need to switch from On Server Development if it's enabled.ĭ has very good instructions about applying patches with Git.įrom your local clone, run the git apply command as per, commit your change, and push back to Pantheon. If you want to patch core or a module, you should use Git. How do I apply a patch from on Pantheon? See Undo Git commits like overwriting Drupal core. Savvy Git users may wonder, "If I create my own pantheon_test_N tag with a higher value N, can I push changes directly to test?" The answer is "yes, yes you can." How do I revert or undo changes? pantheon_test_N and pantheon_live_N are created when you use workflow actions, so you can potentially revert to that state, produce diffs, etc. The tag pantheon.initialize is your initial start state. The "update_drops" tags are from our upstream updates in the past (we don't tag them anymore, but used to).
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |