Skip to content

Feature/2298 automatically assign pull request author as assignee - #2328

Open
QuangAnhLe wants to merge 7 commits into
devonfw:mainfrom
QuangAnhLe:feature/2298-Automatically-Assign-Pull-Request-Author-as-Assignee
Open

Feature/2298 automatically assign pull request author as assignee#2328
QuangAnhLe wants to merge 7 commits into
devonfw:mainfrom
QuangAnhLe:feature/2298-Automatically-Assign-Pull-Request-Author-as-Assignee

Conversation

@QuangAnhLe

@QuangAnhLe QuangAnhLe commented Aug 13, 2026

Copy link
Copy Markdown

This PR fixes #2298

Implemented changes:

Added a new GitHub Actions workflow (.github/workflows/assign-pr-author.yml) that automatically assigns the PR author as assignee when a new Pull Request is opened.

The workflow:

  • Triggers on pull_request event with type opened.
  • Checks whether the PR already has assignees via gh pr view.
  • If no assignees are set, assigns the PR author using gh pr edit --add-assignee.
  • Skips assignment if assignees are already present — existing assignees are never overwritten.
  • Runs as a lightweight job (no checkout, no dependencies) and completes in ~1 second.

Testing instructions

Please add conscise, understandable instructions on how a reviewer can test/verify the functionality of your contribution here:

  1. Open a new Pull Request without assigning anyone.
  2. Navigate to the Actions tab and verify that the Assign PR Author workflow ran successfully.
  3. Confirm that the PR author is automatically listed as assignee on the PR page.
  4. (Optional) Open another PR with an assignee already set — verify that the workflow skips assignment.

Checklist for this PR

Make sure everything is checked before merging this PR. For further info please also see
our DoD.

  • When running mvn clean test locally all tests pass and build is successful
  • PR title is of the form #«issue-id»: «brief summary» (e.g. #921: fixed setup.bat and not feature/921 fixed setup.bat). If no issue ID exists, title only.
  • PR top-level comment summaries what has been done and contains link to addressed issue(s)
  • PR and issue(s) have suitable labels
  • Issue is set to In Progress and assigned to you or there is no issue (might happen for very small PRs)
  • You followed all coding conventions
  • You have added the issue implemented by your PR in CHANGELOG.adoc unless issue is labelled
    with internal
  • You have not changed any dependency in pom.xml files or otherwise if runtime dependencies changed, you have updated our LICENSE.asciidoc
  • You have formulated clear instructions on how to test your contribution under "Testing instructions"

@coveralls

Copy link
Copy Markdown
Collaborator

Coverage Report for CI Build 31700652939

Coverage decreased (-0.008%) to 72.879%

Details

  • Coverage decreased (-0.008%) from the base build.
  • Patch coverage: No coverable lines changed in this PR.
  • 1 coverage regression across 1 file.

Uncovered Changes

No uncovered changes found.

Coverage Regressions

1 previously-covered line in 1 file lost coverage.

File Lines Losing Coverage Coverage
com/devonfw/tools/ide/version/VersionSegment.java 1 90.03%

Coverage Stats

Coverage Status
Relevant Lines: 17548
Covered Lines: 13340
Line Coverage: 76.02%
Relevant Branches: 7757
Covered Branches: 5102
Branch Coverage: 65.77%
Branches in Coverage %: Yes
Coverage Strength: 3.23 hits per line

💛 - Coveralls

@QuangAnhLe QuangAnhLe self-assigned this Aug 14, 2026
@QuangAnhLe QuangAnhLe moved this from 🆕 New to 🏗 In progress in IDEasy board Aug 14, 2026
@QuangAnhLe QuangAnhLe moved this from 🏗 In progress to Team Review in IDEasy board Aug 14, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

Status: Team Review

Development

Successfully merging this pull request may close these issues.

Automatically Assign Pull Request Author as Assignee

2 participants