46 lines
1.7 KiB
Markdown
46 lines
1.7 KiB
Markdown
# Connector for Mobilizon
|
|
|
|
Connector for Mobilizon allows you to display the upcoming events of [Mobilizon](https://joinmobilizon.org/), which is a federated event listing platform, on your WordPress website.
|
|
|
|
More details can be found in the [WordPress Plugin Directory](https://wordpress.org/plugins/connector-mobilizon/).
|
|
|
|
The current changelog can be under [source/changelog.txt](source/changelog.txt).
|
|
|
|
## Development
|
|
|
|
### Setup
|
|
|
|
1. Make sure `npm` and `composer` are installed.
|
|
2. Run: `npm install`
|
|
3. Run: `composer install`
|
|
|
|
### Development build
|
|
|
|
1. Build: `npm run build-dev`
|
|
2. Make sure to keep `changelog.txt` up-to-date.
|
|
|
|
### Release procedure
|
|
|
|
1. Make sure `changelog.txt` is up-to-date. Use a new version number and copy over the new section into `readme.txt`.
|
|
2. Update `package.json` with the same version number.
|
|
3. Update the `package-lock.json`: `npm i --package-lock-only`
|
|
4. Build: `npm run build-prod`
|
|
5. Make sure screenshots are up-to-date.
|
|
6. Copy the built plugin into `/trunk` of SVN.
|
|
7. Create a new tag of the new version: `svn cp trunk tags/<version>`
|
|
8. Check the version number occurrences in both folders.
|
|
9. Commit everything together to the release SVN: `svn ci -m "release version <version>"`
|
|
10. Commit the new version in git with the same message.
|
|
11. Tag the new version: `git tag v<version>`
|
|
12. Push the new tag to the repository: `git push --tags`
|
|
|
|
### Other commands
|
|
|
|
- Run ESLint: `npm run eslint`
|
|
- Run JavaScript code coverage with tests: `npm run coverage`
|
|
- Run tests: `npm test`
|
|
- Delete build folder: `npm run clean`
|
|
- Update PHP dependencies: `composer update`
|
|
- Check for direct PHP dependency updates: `composer outdated --direct`
|
|
- Format code with prettier: `npm run format`
|