Update docker compose

Author: milanmajchrak

.github/pull_request_template.md

@@ -1,31 +1,15 @@
-## References
-_Add references/links to any related issues or PRs. These may include:_
-* Fixes #issue-number (if this fixes an issue ticket)
-* Related to DSpace/RestContract#pr-number  (if a corresponding REST Contract PR exists)
-
-## Description
-Short summary of changes (1-2 sentences).
-
-## Instructions for Reviewers
-Please add a more detailed description of the changes made by your PR. At a minimum, providing a bulleted list of changes in your PR is helpful to reviewers.
-
-List of changes in this PR:
-* First, ...
-* Second, ...
-
-**Include guidance for how to test or review your PR.** This may include: steps to reproduce a bug, screenshots or description of a new feature, or reasons behind specific changes. 
-
-## Checklist
-_This checklist provides a reminder of what we are going to look for when reviewing your PR. You need not complete this checklist prior to creating your PR (draft PRs are always welcome).
-However, reviewers may request that you complete any actions in this list if you have not done so. If you are unsure about an item in the checklist, don't hesitate to ask. We're here to help!_
-
-- [ ] My PR is **created against the `main` branch** of code (unless it is a backport or is fixing an issue specific to an older branch).
-- [ ] My PR is **small in size** (e.g. less than 1,000 lines of code, not including comments & integration tests). Exceptions may be made if previously agreed upon.
-- [ ] My PR **passes Checkstyle** validation based on the [Code Style Guide](https://wiki.lyrasis.org/display/DSPACE/Code+Style+Guide).
-- [ ] My PR **includes Javadoc** for _all new (or modified) public methods and classes_. It also includes Javadoc for large or complex private methods.
-- [ ] My PR **passes all tests and includes new/updated Unit or Integration Tests** based on the [Code Testing Guide](https://wiki.lyrasis.org/display/DSPACE/Code+Testing+Guide).
-- [ ] My PR **includes details on how to test it**. I've provided clear instructions to reviewers on how to successfully test this fix or feature.
-- [ ] If my PR includes new libraries/dependencies (in any `pom.xml`), I've made sure their licenses align with the [DSpace BSD License](https://github.com/DSpace/DSpace/blob/main/LICENSE) based on the [Licensing of Contributions](https://wiki.lyrasis.org/display/DSPACE/Code+Contribution+Guidelines#CodeContributionGuidelines-LicensingofContributions) documentation.
-- [ ] If my PR modifies REST API endpoints, I've opened a separate [REST Contract](https://github.com/DSpace/RestContract/blob/main/README.md) PR related to this change.
-- [ ] If my PR includes new configurations, I've provided basic technical documentation in the PR itself.
-- [ ] If my PR fixes an issue ticket, I've [linked them together](https://docs.github.com/en/issues/tracking-your-work-with-issues/linking-a-pull-request-to-an-issue).
+| Phases            | MP | MM  |  MB  | MR |   JM | Total  |
+|-----------------|----:|----:|----:|-----:|-----:|-------:|
+| ETA                  |  0  |  0  |    0 |     0 |      0 |        0 |
+| Developing      |  0  |  0  |    0 |    0 |      0 |         0 |
+| Review             |  0  |  0  |    0 |    0 |      0 |         0 |
+| Total                |   -  |   -  |   -   |  -    |   -    |         0 |
+| ETA est.             |      |      |       |       |         |         0 |
+| ETA cust.           |   -  |   -  |   -  |   -   |   -     |        0 |
+## Problem description
+### Reported issues
+### Not-reported issues
+## Analysis
+(Write here, if there is needed describe some specific problem. Erase it, when it is not needed.)
+## Problems
+(Write here, if some unexpected problems occur during solving issues. Erase it, when it is not needed.) 

.github/workflows/PM-label-review-process.yml

@@ -0,0 +1,22 @@
+name: Reviewer Label Management
+
+on:
+  pull_request:
+    types: [review_requested]
+  pull_request_review:
+    types: [submitted]
+
+permissions:
+  pull-requests: write
+
+jobs:
+  manage-reviewer-labels:
+    runs-on: ubuntu-latest
+    steps:
+      - name: Apply reviewer labels
+        uses: mazoea/ga-maz/label-review@master
+        with:
+          target-reviewer: 'vidiecan'
+          assigned-label: 'REVIEW-in-progress'
+          completed-label: 'REVIEW-done'
+          github-token: ${{ secrets.GITHUB_TOKEN }}

.github/workflows/build.yml

@@ -77,3 +77,36 @@ jobs:
           name: ${{ matrix.type }} coverage report
           path: 'dspace/target/site/jacoco-aggregate/jacoco.xml'
           retention-days: 14
+
+  # Codecov upload is a separate job in order to allow us to restart this separate from the entire build/test
+  # job above. This is necessary because Codecov uploads seem to randomly fail at times.
+  # See https://community.codecov.com/t/upload-issues-unable-to-locate-build-via-github-actions-api/3954
+  #  codecov:
+  #    # Must run after 'tests' job above
+  #    needs: tests
+  #    runs-on: ubuntu-latest
+  #    steps:
+  #      - name: Checkout
+  #        uses: actions/checkout@v4
+  #
+  #      # Download artifacts from previous 'tests' job
+  #      - name: Download coverage artifacts
+  #        uses: actions/download-artifact@v4
+  #
+  #      # Now attempt upload to Codecov using its action.
+  #      # NOTE: We use a retry action to retry the Codecov upload if it fails the first time.
+  #      #
+  #      # Retry action: https://github.com/marketplace/actions/retry-action
+  #      # Codecov action: https://github.com/codecov/codecov-action
+  #      - name: Upload coverage to Codecov.io
+  #        uses: Wandalen/wretry.action@v1.3.0
+  #        with:
+  #          action: codecov/codecov-action@v4
+  #          # Ensure codecov-action throws an error when it fails to upload
+  #          with: |
+  #            fail_ci_if_error: true
+  #            token: ${{ secrets.CODECOV_TOKEN }}
+  #          # Try re-running action 5 times max
+  #          attempt_limit: 5
+  #          # Run again in 30 seconds
+  #          attempt_delay: 30000