Changes between Initial Version and Version 1 of pushing_changes_to_red


Ignore:
Timestamp:
Dec 15, 2010, 3:35:11 PM (9 years ago)
Author:
Ross
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • pushing_changes_to_red

    v1 v1  
     1== The Red Repository ==
     2
     3The svn repository for red is at
     4
     5{{{
     6mfpl@svn.mayfirst.org/trunk/red .
     7}}}
     8=== Using git-svn ===
     9
     10 * Clone the repository with the following command.
     11
     12{{{
     13git svn clone svn+ssh://mfpl@svn.mayfirst.org/trunk/red
     14}}}
     15
     16 * Update the repository with.
     17
     18{{{
     19git svn fetch
     20}}}
     21
     22 * Merge changes with
     23
     24{{{
     25git rebase
     26}}}
     27
     28 * Committing Changes
     29  * In order to commit changes using git-svn first do a standard git commit method.
     30  * Next commit changes to the svn repository by using:
     31
     32{{{
     33git svn dcommit
     34}}}
     35
     36=== Making Changes Live ===
     37
     38There are two steps to take for making changes live.
     39
     40==== Tag the committed changes ====
     41
     42In order to tag changes to red, you must be in the top level red directory and issue the following command:
     43
     44{{{
     45./svn-create-next-tag
     46}}}
     47
     48==== Updating Red ====
     49
     50After tagging the committed changes cd into the mfpl-servers repository to mfpl-servers/admin/scripts and issue the following command:
     51
     52{{{
     53./execute-directive harry ../directives/red-update/
     54}}}
     55
     56Assuming no error messages, your changes should be live.
     57
     58
     59
     60