CLARIN-DSpace v9/Port #1341 (new_issue_label workflow) to the v9 base - #1434
Merged
Conversation
Source: 882904b (dtq-dev PR #1341) Adds `.github/workflows/new_issue_label.yml`, the `issues: [opened]` workflow that calls `dataquest-dev/gh-actions/start@main` to auto-label newly opened issues. Pure parity pick: the FE 9-base branch already carries the identical workflow (dspace-angular 2b87775fe7), only BE 9-base was missing it. GitHub runs `issues` events exclusively from the repository's default branch (`dtq-dev`), so the copy on `dtq-dev-9-base` is inert today; it exists so a future 9-base -> dtq-dev merge does not delete the workflow. Cherry-picked with no conflict; the blob is byte-identical with `origin/dtq-dev` (e9fcf70). Co-authored-by: Matus Kasak <matus.kasak@dataquest.sk> (cherry picked from commit 882904b) Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
milanmajchrak
force-pushed
the
ufal/port-1341-9-base
branch
from
September 10, 2026 09:21
2958e03 to
225e994
Compare
Collaborator
Author
Local gate outputs (per sync rule 2.5)Base: No Java, config or Flyway migration is touched, so no Maven gate applies to this change. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What
Ports
dataquest-dev/DSpacePR #1341 ("Autolabel for new issues", commit882904ba35) todtq-dev-9-base. Adds one file,.github/workflows/new_issue_label.yml— theissues: [opened]workflow that calls
dataquest-dev/gh-actions/start@mainto auto-label newly opened issues.Sync card: BE-19 (
_sync3/cards/BE-19.md, tranche T4, disposition PORT, size S, risk low).Why
Branch asymmetry, not a behaviour gap. The FE 9-base branch already carries the identical
workflow (
dataquest-dev/dspace-angular2b87775fe7); only BE 9-base was missing it:GitHub dispatches
issuesevents exclusively from the repository's default branch(
dtq-dev), so this copy is inert ondtq-dev-9-basetoday. It exists so that a futuredtq-dev-9-base→dtq-devmerge does not delete the workflow, and so the two 9-basebranches stay symmetric. It changes no CI policy on this branch.
Changes
Clean
git cherry-pick -x 882904ba35; no conflict. One file, +18/−0.Testing
Blob parity with the source branch (AC-BE-19-1):
YAML validity (AC-BE-19-2):
Hunk-level parity — the source patch and this branch's patch are byte-identical, so every
one of the 18 added lines is accounted for:
No Java, config or Flyway migration touched, so no local Maven gate applies; CI checks are the
remaining gate.
🤖 Generated with Claude Code