Workflow to label new issues

[Kasinhou]

Problem description

https://github.com/dataquest-dev/dspace-customers/issues/439

Sync verification

If en.json5 or cs.json5 translation files were updated:

• Run yarn run sync-i18n -t src/assets/i18n/cs.json5 -i to synchronize messages, and changes are included in this PR.

Manual Testing (if applicable)

• Added to testing scenarios

Copilot review

• Requested review from Copilot

Summary by CodeRabbit

• Chores
  • Enhanced automation for issue organization.

[coderabbitai]

📝 Walkthrough

Walkthrough

A new GitHub Actions workflow file was added to automatically label newly opened issues. The workflow triggers on issue creation, runs with permissions to modify issues, and delegates labeling work to an external action configured with the GitHub token.

Changes

GitHub Actions Workflow for Issue Labeling

Layer / File(s)	Summary
Issue auto-labeling workflow .github/workflows/new_issue_label.yml	Workflow listens for newly opened GitHub issues with issues: write permission. A single job runs the dataquest-dev/gh-actions/start@main action with GITHUB_TOKEN configured as the github-token input.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

🚥 Pre-merge checks | ✅ 4 | ❌ 1

❌ Failed checks (1 inconclusive)

Check name	Status	Explanation	Resolution
Description check	❓ Inconclusive	The description is largely incomplete; it only references the problem link but lacks implementation details, analysis, or explanation of the solution.	Add an 'Analysis' section explaining how the workflow addresses the issue, describe what the workflow does, and provide any relevant implementation details.

✅ Passed checks (4 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title clearly and concisely describes the main change: adding a workflow to automatically label new issues.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[coderabbitai]

Actionable comments posted: 1

🤖 Prompt for all review comments with AI agents

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

Inline comments:
In @.github/workflows/new_issue_label.yml:
- Line 15: The workflow currently references the reusable action as
dataquest-dev/gh-actions/start@main which allows upstream changes; replace the
ref with a specific immutable commit SHA (e.g.
dataquest-dev/gh-actions/start@<full-commit-sha>) so the step uses a pinned
commit; update the uses line that currently contains
"dataquest-dev/gh-actions/start@main" to
"dataquest-dev/gh-actions/start@<full-commit-sha>" and commit that change.

🪄 Autofix (Beta)

Fix all unresolved CodeRabbit comments on this PR:

• Push a commit to this branch (recommended)
• Create a new PR with the fixes

---

ℹ️ Review info

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: 01fb0048-09fc-4501-bf1c-f8d025284957

📥 Commits

Reviewing files that changed from the base of the PR and between a616eaf and 84c88b8.

📒 Files selected for processing (1)

• .github/workflows/new_issue_label.yml