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: README.md
+3-3Lines changed: 3 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -26,10 +26,10 @@ If you need to a make a change to the API, complete the following steps:
26
26
1. Update webApiFaker to produce the type of output that you expect.
27
27
1. In the same commit, update the JSON in the README to match what webApiFaker now returns
28
28
1. Add a ticket to pivotal tracker assigned to the backend team and labeled with 'api'
29
-
1. Include a link to the README (perhaps the diff as well) with the version of the API you need
30
-
1. When the API team finishes the change and marks the ticket as 'delivered' determine if the output matches your expectations (check this by running grunt serve:staging)
29
+
1. Include a link to the README (and a diff showing the changes) with the version of the API you need
30
+
1. When the API team finishes the change and marks the ticket as 'delivered' determine if the output matches your expectations (check this manually and/or by running grunt serve:staging)
31
31
1. If the output is as expected, accept the ticket
32
-
1.The the output is incorrect, reject the ticket (possibly ping the person on the backend team as well)
32
+
1.If the output is incorrect, reject the ticket
33
33
34
34
Once the API has been successfully updated, any code that relies on the new data can be merged to master.
0 commit comments