build(ci): migration to github actions

[stachu540]

Prerequisites for Code Changes

• This pull request follows the code style of the project
• I have tested this feature

Changes Proposed

• Migration CI/CD to GitHub Actions

Additional Information

This migration contains:

• ci - which are testing lib in JDK's: 8, 11, 14 and 15 when someone push to some branches and prepare release pushed defined auto-release workflow.
• release - will monitoring main or master branch in specific schedule and only if the workflow is in this repo
• pull_request_open - execute actions when Pull Request was opened
• pull_request_merge - automatically merge Pull Request after all checks are green
• javadoc - deploy javadoc if release has been published
• gradle-wrapper - updating gradle wrapper automatically in specific time

Required Secrets

• GITHUB_TOKEN secret contains token using by @github-actions bot - not needed to set
• OSSRH_USERNAME, OSSRH_PASSPHRASE, GPG_KEY and GPG_PASSPHRASE is for Maven Central deployment - Migration repository to Maven Central #269

Also there is:

• .releaserc.json - Configuration for Semantic Release - BREAKING CHANGES can be removed if you don't putting him in to commit description.
• pr_review.yml - Adding reviewers automatically by pull_request_open.yml
• dependabot.yml - will checks github actions too but i was change it to review both of you and limit to 3 PR's on each day for each build types.

[stachu540]

I can use semantic version using this: https://github.com/marketplace/actions/action-for-semantic-release
rather than release drafter. Action uses Semantic Release as their plugins in this org.

[stachu540]

GH actions has been ready to review. Some automation will be theoretically worked.

There is more feature has been updated in the description. Feel free to check it out.

[stachu540]

I have update one more time. Now will checks approved reviews. If reviews will be more then 1 it will auto-merge using title as commit message (of course will squash commit).

[stachu540]

I will temporary stale this PR before testing it myself. After that i will give feedback and pulling some changes in this branch.

[stachu540]

The changes has been applied. Don't know how about the pull request's action. Anything else leaving to review for @PhilippHeuer

All changes has been test in this sandbox You can change configuration, as you like it.

I will rebase it after will be approved.

[iProdigy]

Should explicitly declare artifactId (see: #243 (comment))

Even this change would not be sufficient (e.g. the tmi module would be named twitch4j-tmi, which is better than twitch4j-rest-tmi, but not quite the desired twitch4j-messaginginterface):

archivesBaseName = artifactId.let {
	val prefixCheck = rootProject.artifactId + "-rest-"
	if (it.startsWith(prefixCheck, true))
		rootProject.artifactId + "-" + it.substring(prefixCheck.length)
	else
		it
}

[stachu540]

removing rest- in module namings will resolves your request

[PhilippHeuer]

I do prefer to group all the api modules with the rest prefix, but we can't change the artifactId's for already released modules - so that one line in each module to set the artifactId is fine.

[PhilippHeuer]

I pushed this branch to https://github.com/twitch4j/twitch4j-ghactions-test / main, so we can test the workflows over there.

accident

[PhilippHeuer]

for the gradle-wrapper workflow:

I added base-branch because it ended up pulling from master/main anyway - it's better to work fully on develop. And i also added the option to manually start the workflow. Example PR here: https://github.com/twitch4j/twitch4j-ghactions-test/pull/28

Next to test will be the MR workflows.

[stachu540]

Unfortunate, this action will not have a pull request title definition to when to be a conventional commit. Wish we could do something of that.