📝 docs: add details of github actions to pipeline approval workflow

Author: kenibrewer

.github/workflows/pipeline_proposals.yml

@@ -85,22 +85,18 @@ jobs:
             }
 
             // Helper function to update issue status and labels
-            async function updateIssueStatus(status, closeReason = null) {
+            async function updateIssueStatus(status) {
               const labels = [];
-              let state = 'open';
 
               switch (status) {
                 case '✅ Approved':
                   labels.push('accepted');
-                  state = 'closed';
                   break;
                 case '❌ Rejected':
                   labels.push('turned-down');
-                  state = 'closed';
                   break;
                 case '⏰ Timed Out':
                   labels.push('timed-out');
-                  state = 'closed';
                   break;
                 default:
                   labels.push('proposed');
@@ -113,17 +109,6 @@ jobs:
                 issue_number: issueNumber,
                 labels: labels
               });
-
-              // Close the issue if needed
-              if (state === 'closed') {
-                await github.rest.issues.update({
-                  owner: org,
-                  repo,
-                  issue_number: issueNumber,
-                  state: 'closed',
-                  state_reason: closeReason || (status === '✅ Approved' ? 'completed' : 'not_planned')
-                });
-              }
             }
 
             // Handle label changes

README.md

@@ -23,15 +23,30 @@ To make a new proposal for a special interest group, please create a new issue i
 
 The curator workflow is as follows:
 
-- [ ] Once a issue is made, update the 'Project' status to 'proposed' (right hand side bar, under 'new-<TYPE>-proposals')
+- [ ] Once a issue is made, a Github Actions workflow will:
+  - Add the 'proposed' label
+  - Create a status comment tracking approvals
 - [ ] Facilitate discussion on the the Issue thread, following the guidance [here](https://nf-co.re/docs/checklists/community_governance/core_team#new-pipeline-proposals-and-onboarding).
 - [ ] Acceptance requires a minimum of OKs from:
   - Two members of the core team.
   - One member of the core team and one member of the maintainers team.
-- [ ] If a proposal is accepted, update both the label AND status to 'accepted', and when closing select 'Close as completed'
-- [ ] If a proposal is turned down, update both the label AND status to 'turned-down', and when closing select 'Close as not planned'
-- [ ] If a proposal is not completed or abandoned after a year, update both the label AND status to 'timed-out', and when closing select 'Close as not planned'
-- [ ] Complete the reemaining new-pipeline onboarding tasks listed [here](https://nf-co.re/docs/checklists/community_governance/core_team#new-pipeline-proposals-and-onboarding)
+- [ ] Core and maintainer members can use the following commands in comments:
+  - `/approve` - to approve the proposal
+  - `/reject` - to reject the proposal
+- [ ] The automation will:
+  - Track approvals and rejections
+  - Update the status comment
+  - Update labels based on the current status
+- [ ] If a proposal is accepted:
+  - Update the status to 'accepted'
+  - Close the issue as 'completed'
+- [ ] If a proposal is turned down:
+  - Update the status to 'turned-down'
+  - Close the issue as 'not planned'
+- [ ] If a proposal is not completed or abandoned after a year:
+  - Add the 'timed-out' label
+  - Close the issue as 'not planned'
+- [ ] Complete the remaining new-pipeline onboarding tasks listed [here](https://nf-co.re/docs/checklists/community_governance/core_team#new-pipeline-proposals-and-onboarding)
 
 ### Special Interest Groups