@@ -258,9 +258,12 @@ sandbox client id and app secret)."
The perk data is stored in the `perks.json` file at the root of the project.
Updating the contents of this file should not be done manually as it required strict synchronization between the tordonate app and CiviCRM.
Updating the contents of this file should not be done manually as it required
strict synchronization between the tordonate app and CiviCRM.
Instead, the data should be [updated first in CiviCRM](service/crm#updating-premiums), then exported using the [dedicated JSON export page](https://crm.torproject.org/civicrm/tpa-perks-json).
Instead, the data should be [updated first in
CiviCRM](service/crm#updating-premiums), then exported using the [dedicated
This generated data can directly replace the existing `perks.json` file.
...
...
@@ -276,7 +279,9 @@ To do this in the GitLab web interface, follow these instructions:
- Check "create a merge request for this change"
- Then click "commit changes" and continue with the merge-request.
Once the changes are merged, they will be deployed to staging automatically. To deploy the changes to production, after testing, trigger the manual "deploy-prod" CI job.
Once the changes are merged, they will be deployed to staging automatically. To
deploy the changes to production, after testing, trigger the manual
