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
+4-4Lines changed: 4 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -40,13 +40,13 @@ Then, Rollup will bundle the code into a single file at `dist/plugin.js`. This f
40
40
41
41
Build and validate the web and native projects.
42
42
43
-
This is useful to run in CI to verify that the plugin builds for all platforms.
43
+
This is run in CI to verify that the plugin builds for all platforms.
44
44
45
45
#### `npm run lint` / `npm run fmt`
46
46
47
47
Check formatting and code quality, autoformat/autofix if possible.
48
48
49
-
This template is integrated with ESLint, Prettier, and SwiftLint. Using these tools is completely optional, but the [Capacitor Community](https://github.com/capacitor-community/) strives to have consistent code style and structure for easier cooperation.
49
+
The `lint` command is run in CI. We recommend running `lint`and/or `fmt` before opening a PR,
50
50
51
51
## Commits/PR's
52
52
@@ -62,6 +62,6 @@ Publishing is automated based on the branch committed to. When a commit or merge
62
62
| next | next (these are betas/alphas) | next |@capacitor/filesystem@7.1.0-next.1 |
63
63
| main | latest | latest |@capacitor/filesystem@7.1.0 |
64
64
65
-
- In general new developments will go straight to `main`. If we want to have non-stable versions (e.g. for new Capacitor versions or when there are many changes), we may use `next` or `development` branch, and then once they are ready for stable version, open a PR to main (should be rebased to keep history).
65
+
- In general new developments will go straight to `main`. If we want to have non-stable versions (e.g. for new Capacitor versions or when there are many changes), we may use `next` or `development` branch, and then once they are ready for stable version, open a PR to main (should be merged to keep commit hashes for `semantic-release`).
66
66
67
-
> **Note**: The [`files`](https://docs.npmjs.com/cli/v7/configuring-npm/package-json#files) array in `package.json` specifies which files get published. If you rename files/directories or add files elsewhere, you may need to update it.
67
+
> **Note**: The [`files`](https://docs.npmjs.com/cli/configuring-npm/package-json) array in `package.json` specifies which files get published. If you rename files/directories or add files elsewhere, you may need to update it.
0 commit comments