Merge pull request #131 from lilaboc/fix-127 #130

	# This workflow will build a package using Maven and then publish it to GitHub packages when a release is created
	# For more information see: https://github.com/actions/setup-java/blob/main/docs/advanced-usage.md#apache-maven-with-a-settings-path

	name: Deploy Javadoc

	#on:
	# release:
	# types: [created]

	on:
	push:
	branches:
	- main

	jobs:
	publish:
	runs-on: ubuntu-latest
	steps:
	- uses: actions/checkout@v4
	with:
	token: ${{ secrets.GITHUB_TOKEN }}
	ref: javadoc
	persist-credentials: false # otherwise, the token used is the GITHUB_TOKEN, instead of your personal access token.
	fetch-depth: 0 # otherwise, there would be errors pushing refs to the destination repository.
	- name: merge changes
	run: \|
	git config --local user.email "41898282+github-actions[bot]@users.noreply.github.com"
	git config --local user.name "github-actions[bot]"
	git merge origin/main
	- name: Set up JDK 17
	uses: actions/setup-java@v4
	with:
	java-version: '17'
	distribution: 'temurin'
	cache: maven
	- name: Generate javadoc
	run: \|
	mvn javadoc:javadoc
	git add .
	git commit -m "javadoc updates"
	- name: Push changes
	uses: ad-m/github-push-action@master
	with:
	github_token: ${{ secrets.GITHUB_TOKEN }}
	branch: javadoc

Provide feedback