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
50 Commits 2 Branches 26 Tags 18 MiB
PHP 60.3%
JavaScript 39.7%
Go to file
Daniel Waxweiler a8584096d8 localise dates 2021-05-04 11:16:18 +02:00
.github/workflows let build only run on Node 12.x 2021-05-04 10:14:58 +02:00
assets add plugin icon 2021-04-20 21:19:18 +02:00
source/connector-mobilizon localise dates 2021-05-04 11:16:18 +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 improve release procedure steps 2021-04-20 21:44:10 +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
icon.afdesign add plugin icon 2021-04-20 21:19:18 +02:00
package-lock.json update dev dependencies 2021-05-03 21:52:13 +02:00
package.json update dev dependencies 2021-05-03 21:52:13 +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. Update the package-lock.json: npm i --package-lock-only
  4. Build: npm run build-prod
  5. Determine minimum PHP version for code and update package.json if needed: ./vendor/bin/phpcompatinfo analyser:run ./source
  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 occurences in both folders.
  10. Commit everything together to the release SVN: svn ci -m "release version <version>"
  11. Commit and 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