Mobilizon
/
connector-wordpress
mirror of https://github.com/dwaxweiler/connector-mobilizon
1
0
Fork 0
Code Issues Releases Wiki Activity
Connector per Mobilizon ti permette di visualizzare i prossimi eventi di Mobilizon sul tuo sito WordPress. https://mobilizon.it
203 Commits 2 Branches 26 Tags 18 MiB
PHP 60.3%
JavaScript 39.7%
Go to file
Daniel Waxweiler 718119d299 change names 2023-05-21 14:57:54 +02:00
.github/workflows add qodana 2023-02-12 17:20:20 +01:00
.husky add eslint and prettier to pre-commit hook 2021-12-09 19:54:38 +01:00
assets release version 0.10.0 2022-06-19 09:48:06 +02:00
source change names 2023-05-21 14:57:54 +02:00
tests fix tests 2023-05-21 14:47:36 +02:00
.eslintrc.json add Gutenberg events list block 2022-06-09 20:09:08 +02:00
.gitignore fix tests 2023-05-21 14:47:36 +02:00
.gulp.json update dev dependencies ava, eslint, eslint-plugin-ava and migrate to ES modules 2022-01-09 12:11:24 +01:00
.prettierignore add prettier 2021-12-09 19:46:19 +01:00
.prettierrc.json add prettier 2021-12-09 19:46:19 +01:00
LICENSE.md create LICENSE.md 2021-07-31 16:01:23 +02:00
README.md add phpunit to npm run test 2023-05-21 14:52:09 +02:00
babel.config.json Merge branch 'main' into block 2021-12-14 15:33:07 +01:00
composer.json fix tests 2023-05-21 14:47:36 +02:00
composer.lock fix tests 2023-05-21 14:47:36 +02:00
gulpfile.cjs Merge branch 'main' into block 2022-06-03 23:32:46 +02:00
icon.afdesign add plugin icon 2021-04-20 21:19:18 +02:00
package-lock.json update dependencies 2023-05-07 18:00:02 +02:00
package.json add phpunit to npm run test 2023-05-21 14:52:09 +02:00
phpunit.xml fix tests 2023-05-21 14:47:36 +02:00
qodana.yaml remove bootstrap from qodana.yaml 2023-03-29 22:47:59 +02:00
webpack.config.cjs add Gutenberg events list block 2022-06-09 20:09:08 +02:00

README.md

Connector for Mobilizon

Connector for Mobilizon allows you to display the upcoming events of Mobilizon, which is a federated event listing platform, on your WordPress website.

More details can be found in the WordPress Plugin Directory.

The current changelog can be found under 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.
  2. Use a new version number and copy over the new section into readme.txt.
  3. Update package.json with the same version number.
  4. Update the package-lock.json: npm i --package-lock-only
  5. Build: npm run build-prod
  6. Make sure screenshots are up-to-date.
  7. Copy the built plugin into /trunk of SVN.
  8. Create a new tag of the new version: svn cp trunk tags/<version>
  9. Check the version number occurrences in both folders.
  10. Commit everything together to the release SVN: svn ci -m "release version <version>" Make sure to add new files beforehand.
  11. Commit the new version in git with the same message.
  12. Tag the new version: git tag v<version>
  13. 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
  • Generate vendor/autoload.php file after creating new class: composer dump-autoload