Recognize localization as trigger

[NotMyFault]

Depends on jenkinsci/.github#81

[NotMyFault]

@timja any plans how we want to proceed with this PR? This label would be the one I'd add to the default workflow.

[jglick]

@timja do you recall if this configuration is even still used? jenkins-infra/interesting-category-action#4 is the relevant spot, I thought. In which case

jenkins-maven-cd-action/run.sh

Lines 3 to 6 in a0a2c86

	if [ $GITHUB_EVENT_NAME = check_run ]
	then
	gh api /repos/$GITHUB_REPOSITORY/releases | jq -e -r '.[] | select(.draft == true and .name == "next") | .body' | egrep "$INTERESTING_CATEGORIES"
	fi

and

jenkins-maven-cd-action/action.yaml

Lines 10 to 16 in a0a2c86

	INTERESTING_CATEGORIES:
	required: true
	description: |
	Regexp of emojis from https://github.com/jenkinsci/.github/blob/master/.github/release-drafter.yml representing changes of interest to users.
	By default excludes 📦📝👻🚦 under the assumption these do not normally merit a release.
	Ignored when using workflow_dispatch (explicit release); when using the check_run trigger (automatic), the release is skipped unless the draft changelog matches.
	default: '[💥🚨🎉🐛⚠🚀🌐👷]|:(boom|tada|construction_worker):'

could be deleted and

jenkins-maven-cd-action/action.yaml

Line 20 in a0a2c86

- run: GITHUB_TOKEN=${{ inputs.GITHUB_TOKEN }} MAVEN_USERNAME=${{ inputs.MAVEN_USERNAME }} MAVEN_TOKEN=${{ inputs.MAVEN_TOKEN }} INTERESTING_CATEGORIES='${{ inputs.INTERESTING_CATEGORIES }}' $GITHUB_ACTION_PATH/run.sh

amended? Or did you leave this clause for compatibility after introducing interesting-category-action?

[timja]

I think it was for compatibility can't remember where the discussion at the time was though.