You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: source/WorkingPractices/macros.rst
+6-1Lines changed: 6 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -43,6 +43,11 @@ Within the file a blank upgrade macro will typically look like this:
43
43
# Input your macro commands here
44
44
return config, self.reports
45
45
46
+
Note: The BEFORE_TAG should match the AFTER_TAG of the previous macro in the chain. So if this is not the first macro since the release then the BEFORE_TAG will be the version number with an added ticket number as well. For example:
47
+
48
+
.. code-block::
49
+
50
+
BEFORE_TAG = "vn13.0_t123"
46
51
47
52
Example of an upgrade macro
48
53
---------------------------
@@ -132,4 +137,4 @@ The ``vnXX.Y_tTTTT`` option must match the After Tag of your upgrade macro. When
132
137
133
138
.. tip::
134
139
135
-
The apply_macros script requires python >= 3.9. At the Met Office this can be achieved by ``module load scitools``.
140
+
The apply_macros script requires python >= 3.9. At the Met Office this can be achieved by ``module load scitools``.
0 commit comments