Changes
Page history
service/donate: tweaks
authored
Oct 13, 2025
by
Jérôme Charaoui
Show whitespace changes
Inline
Side-by-side
service/donate.md
View page @
6b7d886e
...
@@ -258,8 +258,8 @@ sandbox client id and app secret)."
...
@@ -258,8 +258,8 @@ sandbox client id and app secret)."
The perk data is stored in the
`perks.json`
file at the root of the project.
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
Updating the contents of this file should
**
not
**
be done manually as it
strict synchronization between the tordonate app and CiviCRM.
requires
strict synchronization between the tordonate app and CiviCRM.
Instead, the data should be
[
updated first in
Instead, the data should be
[
updated first in
CiviCRM
](
service/crm#updating-premiums
)
, then exported using the
[
dedicated
CiviCRM
](
service/crm#updating-premiums
)
, then exported using the
[
dedicated
...
@@ -267,14 +267,15 @@ JSON export page](https://crm.torproject.org/civicrm/tpa-perks-json).
...
@@ -267,14 +267,15 @@ JSON export page](https://crm.torproject.org/civicrm/tpa-perks-json).
This generated data can directly replace the existing
`perks.json`
file.
This generated data can directly replace the existing
`perks.json`
file.
To do this in the GitLab web interface, follow these instructions:
To do this
us
in
g
the GitLab web interface, follow these instructions:
-
Go to: https://gitlab.torproject.org/tpo/web/donate-neo/-/blob/main/perks.json
-
Go to: https://gitlab.torproject.org/tpo/web/donate-neo/-/blob/main/perks.json
-
Click "Edit (single file)"
-
Click "Edit (single file)"
-
Delete the text (click in the text box, select all, delete)
-
Delete the text (click in the text box, select all, delete)
-
Paste the text copied from CiviCRM
-
Paste the text copied from CiviCRM
-
Click "Commit changes"
-
Click "Commit changes"
-
Commit message: Adapt the commit message to be a bit more descriptive (ex: "2025 YEC perks")
-
Commit message: Adapt the commit message to be a bit more descriptive (eg:
"2025 YEC perks", and include the issue number if one exists)
-
Branch: commit to a new branch, call it something like "yec2025"
-
Branch: commit to a new branch, call it something like "yec2025"
-
Check "create a merge request for this change"
-
Check "create a merge request for this change"
-
Then click "commit changes" and continue with the merge-request.
-
Then click "commit changes" and continue with the merge-request.
...
...
...
...