backport: bitcoin#27888, bitcoin#27941, bitcoin#28213, bitcoin#19690, bitcoin#27469, bitcoin#27786, bitcoin#27907 #14831

	name: "Label Merge Conflicts"
Check warning on line 1 in .github/workflows/label-merge-conflicts.yml View workflow run for this annotation GitHub Actions / Label Merge Conflicts Workflow execution policy warning (evaluate mode) On November 2, 2026, GitHub will restrict `pull_request_target` on public repositories by default. To continue allowing the event trigger, configure an Actions policy. Learn more: https://gh.io/securely-using-pull_request_target#default-policy-for-pull_request_target
	on:
	# So that PRs touching the same files as the push are updated
	push:
	# So that the `dirtyLabel` is removed if conflicts are resolve
	# We recommend `pull_request_target` so that github secrets are available.
	# In `pull_request` we wouldn't be able to change labels of fork PRs
	pull_request_target:
	types: [synchronize]

	permissions:
	contents: read
	pull-requests: write
	# issues: write is required so the action can manage labels and post comments on PRs
	issues: write
	# Enforce other not needed permissions are off
	actions: none
	checks: none
	deployments: none
	#metadata: read
	packages: none
	repository-projects: none
	security-events: none
	statuses: none

	jobs:
	main:
	runs-on: ubuntu-latest
	steps:
	- name: check if prs are dirty
	uses: eps1lon/actions-label-merge-conflict@v3.1.0
	with:
	dirtyLabel: "needs rebase"
	repoToken: "${{ secrets.GITHUB_TOKEN }}"
	commentOnDirty: "This pull request has conflicts, please rebase."
	#commentOnClean: "Conflicts have been resolved. A maintainer will review the pull request shortly."

Navigation Menu