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
{{ message }}
This repository was archived by the owner on Aug 8, 2023. It is now read-only.
Please include a summary of the change. Please also include relevant motivation and context. List any dependencies that are required for this change.
4
+
5
+
<!-- If this PR fixes an issue, please specify issue #. -->
6
+
7
+
## Type of change
8
+
9
+
-[ ] Bug fix (non-breaking change which fixes an issue)
10
+
-[ ] New feature (non-breaking change which adds functionality)
11
+
-[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
12
+
-[ ] Documentation update
13
+
14
+
## Changes
15
+
16
+
- (change1)
17
+
18
+
# How to test this PR?
19
+
20
+
Please describe the tests that you ran to verify your changes. Provide instructions so we can reproduce. Please also list any relevant details for your test configuration
21
+
22
+
# Checklist:
23
+
24
+
-[ ] My code follows the style guidelines of this project (`npm run lint`)
25
+
-[ ] I have performed a self-review of my own code
26
+
-[ ] I have commented my code, particularly in hard-to-understand areas
27
+
-[ ] I have made corresponding changes to the documentation (`README.md` and `CHANGELOG.md`)
28
+
-[ ] I have added tests that prove my fix is effective or that my feature works
29
+
-[ ] New and existing unit tests pass locally with my changes (`npm test`)
Because Salesforce OCAPI is not publicly available, you need to have a running instance that you can test against. In the test folder, there is a file `config.json` that has the example configuration for your environment. Simply update the file with your instance information
We use Circle CI to protect the `develop` and `master` branch to make sure the builds follows the code style and passes all tests. For every pull request, it is required to pass ALL checks including the following tests:
140
+
141
+
- Linting: `npm run lint`
142
+
- Unit Tests: `npm run test`
143
+
144
+
## 📦 Build and Deployment
145
+
146
+
At Mobify, we practice several branching strategies, [Release Deployment](https://github.com/mobify/branching-strategy/blob/master/release-deployment.md) is a strategy for projects where feature gets bundled into a release periodically. `master` contains the code for current version, `develop` has the features that is under development and waiting to be released. For new features and bug fixes, please propose pull requests to merge into `develop`.
147
+
148
+
This package is distributed on npm, on every release, we run scripts to automatically merge `develop` into `master`, test the build in Circle CI as well as publish the package on NPM.
149
+
150
+
### Changelog
151
+
152
+
To understand the change between versions, please read [CHANGELOG.md](./CHANGELOG.md). Note that it is required to have a `# To be released` section filled out if you are planning to make pull requests that include new features or bug fixes.
153
+
154
+
Example:
155
+
```markdown
156
+
## To be released
157
+
- Update npm package to ship with three builds: `UMD`, `CommonJS` and `ES2015` [#4](https://github.com/mobify/commercecloud-ocapi-client/pull/4)
0 commit comments