Automatically add new Issues to "DSpace Backlog" project board#796
Merged
Automatically add new Issues to "DSpace Backlog" project board#796
Conversation
Member
Author
|
Merging immediately, as I've tested this in a personal repo and the https://github.com/DSpace/Rest7Contract repo and it works in both those places. |
4science-it
pushed a commit
to 4Science/dspace-angular
that referenced
this pull request
Sep 20, 2023
[DSC-1207] fixed “search tools” button behavior Approved-by: Andrea Barbasso Approved-by: Vincenzo Mecca
kosarko
pushed a commit
to ufal/dspace-angular
that referenced
this pull request
Mar 6, 2025
…compose correct redirect url (DSpace#796)
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
1 participant
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.
(Copy of DSpace/DSpace#2861 to this repository)
This creates a new "issue_opened.yml" workflow configuration which enables a GitHub Action for all newly created Issues which are either unlabeled or labeled with
needs triage.More specifically, the Create Project Card action is run to check for new issues to add to the DSpace Backlog project board. The purpose of this Board is to capture incoming issues that need triaging/scheduling for a specific release...although there's also an "Unscheduled backlog" column on that board for anything that is currently unscheduled.
At this time, only issues flagged as
needs triage(which will be added by default) or unlabeled will go on this board. Other issues will be assumed to have already been triaged to a specific release board (e.g. the DSpace 7.1 board or similar).I'm creating this PR simply as documentation of this decision & to test the process in GitHub (to make sure it works as expected). Additional GitHub actions may be forthcoming as well!