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: CONTRIBUTING.md
+3-1Lines changed: 3 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -84,7 +84,9 @@ To pull the latest code from `canary` into `integrations/makeswift`, follow the
84
84
```
85
85
86
86
> [!IMPORTANT]
87
-
> It is very important that you do not use the merge button in the GitHub UI to merge your PR. The problem with the "Squash and merge" or "Rebase and merge" button in GitHub is that it **rewrites history and throws away your local merge commit**. Instead, locally rebasing your `integrations/makeswift` branch onto your `{new-branch-name}` branch preserves the merge commit from step 4, which will properly set the new merge base for future merges from `canary` into `integrations/makeswift`.
87
+
> We have added a GitHub Ruleset to protect against this, but it's worth explicitly documenting here for posterity: It is very important that we do not "Squash and merge" or "Rebase and merge" our changes onto `integrations/makeswift`. Instead, we should either merge the PR with a traditional merge commit (the button in the GitHub PR UI should say "Merge pull request"), or locally rebase the `integrations/makeswift` branch onto the `{new-branch-name}` branch (as illustrated in the step above). Either of these options will correctly preserve the merge commit from step 4 in the history of the `integrations/makeswift` branch, which will then set the new merge base for future merges from `canary` into `integrations/makeswift`.
88
+
>
89
+
> If you are unsure whether or not you've done this correctly, you can run `git merge canary` from `integrations/makeswift` after rebasing in the step above; if you see "Already up to date.", you followed the steps correctly (with one caveat: in the case that new commits have been pushed to `canary` since the last time you merged, then you may see a new merge commit/potential conflicts for only those new commits).
88
90
89
91
7. Push the changes up to GitHub, which will automatically close the open PR from step 5.
Copy file name to clipboardExpand all lines: core/.env.test.example
+19-1Lines changed: 19 additions & 1 deletion
Original file line number
Diff line number
Diff line change
@@ -3,6 +3,8 @@
3
3
# For example, if BIGCOMMERCE_CHANNEL_ID=1 in .env.local, but BIGCOMMERCE_CHANNEL_ID=5 in this file, the test environment will use BIGCOMMERCE_CHANNEL_ID=5
4
4
5
5
# Access token client ID and client secret are required for JWT login tests. If not provided, tests that require these will be skipped.
6
+
# If provided, ensure the API account associated with this client ID/secret pair has the following scope:
7
+
# - Customers login: login
6
8
BIGCOMMERCE_CLIENT_ID=
7
9
BIGCOMMERCE_CLIENT_SECRET=
8
10
@@ -28,7 +30,23 @@ TEST_CUSTOMER_ID=1
28
30
TEST_CUSTOMER_EMAIL=example@test.com
29
31
TEST_CUSTOMER_PASSWORD=Password1
30
32
31
-
# Used to create customer accounts for testing purposes if no existing customer account is provided
33
+
# Used to create/update/delete store data for testing purposes
34
+
# Some tests will not pass without a BIGCOMMERCE_ACCESS_TOKEN, even with TESTS_READ_ONLY set to true
35
+
# This is due to the test API client sending GET (read-only) API requests
36
+
# Create a token with the following scopes:
37
+
# - Content: read-only
38
+
# - Products: read-only
39
+
# - Channel listings: read-only
40
+
# - Channel settings: read-only
41
+
# - Information & settings: read-only
42
+
# - Customers: read-only
43
+
# - Orders: read-only
44
+
# When TESTS_READ_ONLY is false, you'll need additional scopes:
45
+
# - Products: modify
46
+
# - Content: modify
47
+
# - Customers: modify
48
+
# - Marketing: modify
49
+
# - Orders: modify
32
50
BIGCOMMERCE_ACCESS_TOKEN=
33
51
34
52
# The default product ID to use for tests. This needs to be a product without variants (simple)
Copy file name to clipboardExpand all lines: core/CHANGELOG.md
-4Lines changed: 0 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -189,7 +189,6 @@
189
189
### Minor Changes
190
190
191
191
-[#1491](https://github.com/bigcommerce/catalyst/pull/1491)[`313a591`](https://github.com/bigcommerce/catalyst/commit/313a5913181a144b53cb12208132f4a9924e2256) Thanks [@jorgemoya](https://github.com/jorgemoya)! - Bump `next-intl` which includes [some minor changes and updated APIs](<(https://next-intl-docs.vercel.app/blog/next-intl-3-22)>):
192
-
193
192
- Use new `createNavigation` api.
194
193
- Pass `locale` to redirects.
195
194
-`setRequestLocale` is no longer unstable.
@@ -285,7 +284,6 @@
285
284
-[#1362](https://github.com/bigcommerce/catalyst/pull/1362)[`0814afe`](https://github.com/bigcommerce/catalyst/commit/0814afefca00b2497dddb0622df45f4d50865882) Thanks [@deini](https://github.com/deini)! - If app is not running on Vercel's infra, `<Analytics />` and `<SpeedInsights />` are not rendered.
286
285
287
286
Opt-out of vercel analytics and speed insights by setting the following env vars to `true`
288
-
289
287
-`DISABLE_VERCEL_ANALYTICS`
290
288
-`DISABLE_VERCEL_SPEED_INSIGHTS`
291
289
@@ -374,7 +372,6 @@
374
372
-[#1278](https://github.com/bigcommerce/catalyst/pull/1278)[`f8553c6`](https://github.com/bigcommerce/catalyst/commit/f8553c6c9fb35ab7a143fabd60719c8156269448) Thanks [@jorgemoya](https://github.com/jorgemoya)! - Fix wrapping author text in BlogPostCard.
375
373
376
374
-[#1322](https://github.com/bigcommerce/catalyst/pull/1322)[`77ecb4b`](https://github.com/bigcommerce/catalyst/commit/77ecb4bb4f527e079788b0f9dff2468e92d0bc1a) Thanks [@jorgemoya](https://github.com/jorgemoya)! - Split auth forms to four different pages:
377
-
378
375
- /login
379
376
- /register
380
377
- /reset
@@ -424,7 +421,6 @@
424
421
-[#1194](https://github.com/bigcommerce/catalyst/pull/1194)[`b455b05`](https://github.com/bigcommerce/catalyst/commit/b455b05a6121b005bd5147a25c964b9554b1b350) Thanks [@BC-krasnoshapka](https://github.com/BC-krasnoshapka)! - Add basic support for Google Analytics via [Big Open Data Layer](https://developer.bigcommerce.com/docs/integrations/hosted-analytics). BODL and GA4 integration is encapsulated in `bodl` library which hides current complexity and limitations that will be improved in future. It can be extended with more events and integrations with other analytics providers later. Data transformation from Catalyst data models to BODL and firing events is done in client components, as only frontend events are supported by BODL for now.
0 commit comments