Item don't render in edit item relationships type for relationship types which are tilted on the item to which it is not tilted #918
This file contains 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
| # This workflow runs whenever a new issue is created | |
| name: Issue opened | |
| on: | |
| issues: | |
| types: [opened] | |
| permissions: {} | |
| jobs: | |
| automation: | |
| runs-on: ubuntu-latest | |
| steps: | |
| # Add the new issue to a project board, if it needs triage | |
| # See https://github.com/actions/add-to-project | |
| - name: Add issue to triage board | |
| # Only add to project board if issue is flagged as "needs triage" or has no labels | |
| # NOTE: By default we flag new issues as "needs triage" in our issue template | |
| if: (contains(github.event.issue.labels.*.name, 'needs triage') || join(github.event.issue.labels.*.name) == '') | |
| uses: actions/[email protected] | |
| # Note, the authentication token below is an ORG level Secret. | |
| # It must be created/recreated manually via a personal access token with admin:org, project, public_repo permissions | |
| # See: https://docs.github.com/en/actions/configuring-and-managing-workflows/authenticating-with-the-github_token#permissions-for-the-github_token | |
| # This is necessary because the "DSpace Backlog" project is an org level project (i.e. not repo specific) | |
| with: | |
| github-token: ${{ secrets.TRIAGE_PROJECT_TOKEN }} | |
| project-url: https://github.com/orgs/DSpace/projects/24 |