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
38 Commits 2 Branches 26 Tags 18 MiB
PHP 60.3%
JavaScript 39.7%
Go to file
Daniel Waxweiler 72f2c12343 extract two methods from main file 2021-04-13 21:10:28 +02:00
assets release version 0.2.0 2021-01-15 21:32:45 +01:00
source/connector-mobilizon extract two methods from main file 2021-04-13 21:10:28 +02:00
.eslintrc.json add ESLint 2021-04-05 17:53:47 +02:00
.gitignore add JS coverage tool 2021-04-09 13:08:29 +02:00
README.md add JS coverage tool 2021-04-09 13:08:29 +02:00
composer.json first commit 2021-01-08 14:08:40 +01:00
composer.lock updated dependencies 2021-03-10 16:14:37 +01:00
gulpfile.js add ESLint 2021-04-05 17:53:47 +02:00
package-lock.json update dev dependencies 2021-04-11 22:47:49 +02:00
package.json enable full JS source code coverage 2021-04-13 20:17:07 +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.

Development

Setup

  1. Make sure npm and composer are installed.
  2. Run: npm install
  3. Run: php composer.phar 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. Build: npm run build-prod
  4. Determine minimum PHP version for code and update package.json if needed: ./vendor/bin/phpcompatinfo analyser:run ./source
  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 occurences in both folders.
  9. Commit everything together: svn ci -m "release version <version>"
  10. Tag the new version in git too.

Other commands

  • Run ESLint: npm run eslint
  • Run JavaScript code coverage with tests: npm run coverage
  • Run tests: npm test
  • Delete build folder: gulp clean