build: add workflow and script to label PRs with merge conflicts

[Planeshifter]

Resolves stdlib-js/metr-issue-tracker#131.

Description

What is the purpose of this pull request?

This pull request:

• adds a workflow and script to label PRs with merge conflicts as such.

Related Issues

Does this pull request have any related issues?
None

Questions

Any questions for reviewers of this pull request?

As currently implemented, the script only fetches the latest 100 open PRs to process, with no pagination implemented. This seems sufficient to me to avoid having to deal with cursor-based pagination in the GitHub GraphQL API, but it's a caveat to keep in mind and which could be revisited if deemed necessary; one alternative would be to only process the PRs updated from the last workflow run.

Other

Any other information relevant to this pull request? This may include screenshots, references, and/or implementation notes.

No.

Checklist

Please ensure the following tasks are completed before submitting this pull request.

• Read, understood, and followed the contributing guidelines.

AI Assistance

When authoring the changes proposed in this PR, did you use any kind of AI assistance?

• Yes
• No

If you answered "yes" above, how did you use AI assistance?

• Code generation (e.g., when writing an implementation or fixing a bug)
• Test/benchmark generation
• Documentation (including examples)
• Research and understanding

Disclosure

If you answered "yes" to using AI assistance, please provide a short disclosure indicating how you used AI assistance. This helps reviewers determine how much scrutiny to apply when reviewing your contribution. Example disclosures: "This PR was written primarily by Claude Code." or "I consulted ChatGPT to understand the codebase, but the proposed changes were fully authored manually by myself.".

---

@stdlib-js/reviewers

[Planeshifter]

/stdlib update-copyright-years

[kgryte]

Overall, this looks good to me. Given the recent reorganization of scripts in .github/workflows, @Planeshifter do you want to go ahead and move the check_merge_conflicts_prs script to a sub-folder?

[socket-security]

Warning

Review the following alerts detected in dependencies.

According to your organization's Security Policy, it is recommended to resolve "Warn" alerts. Learn more about Socket for GitHub.

Action	Severity	Alert  (click "▶" to expand/collapse)
Warn		Critical CVE: Unsafe defaults in npm remark-html`` CVE: GHSA-9q5w-79cv-947m Unsafe defaults in remark-html (CRITICAL) Affected versions: = 14.0.0; < 13.0.2; >= 14.0.0 < 14.0.1 Patched version: 13.0.2 From: package.json → npm/remark-html@10.0.0 ℹ Read more on: This package | This alert | What is a critical CVE? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support@socket.dev. Suggestion: Remove or replace dependencies that include known critical CVEs. Consumers can use dependency overrides or npm audit fix --force to remove vulnerable dependencies. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/remark-html@10.0.0. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.

View full report

[Planeshifter]

/stdlib update-copyright-years

[socket-security]

Review the following changes in direct dependencies. Learn more about Socket for GitHub.

Diff	Package	Supply Chain Security	Vulnerability	Quality	Maintenance	License
	remark-html@​10.0.0
	read-installed@​4.0.3
	mathjax-node-sre@​3.0.3
	remark-vdom@​8.0.0
	remark-lint-no-trailing-spaces@​3.0.2
	proxyquire-universal@​2.1.0
	process@​0.11.10
	proxyquire@​2.1.3
	lunr@​2.3.9
	virtual-dom@​2.1.1
	tap-xunit@​2.4.1
	vdom-to-html@​2.3.1
	mathjax-node@​2.1.1
	plato@​1.7.0
	tap-spec@​5.0.0
	uglifyify@​5.0.2
	tap-summary@​4.0.0
	parse-link-header@​1.0.1
	proxyquireify@​3.2.1
	remark-lint-no-auto-link-without-protocol@​1.0.4
	remark-lint-no-inline-padding@​1.0.5
	remark-slug@​5.1.2
	to-vfile@​6.1.0
	remark-unlink@​2.1.2
	mkdirp@​0.5.6
	jsdoc@​3.6.11
	resolve@​1.22.11
	remark-lint-linebreak-style@​1.0.4
	remark-lint-no-html@​1.0.4
	remark-lint-no-paragraph-content-indent@​1.0.7
	unist-util-visit@​2.0.3
	remark-lint-no-heading-like-paragraph@​1.0.4
	remark-lint-no-reference-like-url@​1.0.5
	remark-lint-no-duplicate-headings-in-section@​1.0.5
See 74 more rows in the dashboard

View full report