• Type: Icon: Sub-task Sub-task
    • Resolution: Fixed
    • Priority: Icon: Major - P3 Major - P3
    • 6.4.0
    • Affects Version/s: None
    • Component/s: None
    • 0
    • Not Needed
    • Hide

      Create a copy of the Kickoff Template with the issue key (NODE-XXX) in the filename and share a link to the new doc via this field.

      Show
      Create a copy of the Kickoff Template with the issue key (NODE-XXX) in the filename and share a link to the new doc via this field.
    • Not Needed
    • Hide

      1. What would you like to communicate to the user about this feature?
      2. Would you like the user to see examples of the syntax and/or executable code and its output?
      3. Which versions of the driver/connector does this apply to?

      Show
      1. What would you like to communicate to the user about this feature? 2. Would you like the user to see examples of the syntax and/or executable code and its output? 3. Which versions of the driver/connector does this apply to?

      See parent NODE-5348

      Implementation notes from Kickoff:

      • We will make the following changes directly to release_notes.yml, it can resolve the difference between a comment trigger and a workflow_dispatch trigger for sourcing the releasePR number.
      • release_notes adds the following trigger: `on: {  issue_comment: {  types: [created] }}`
      • When a comment triggers the workflow 
      • Use ${{ github.event.comment.body == 'run release_notes' }} to check for the correct trigger string
      • Use ${{ github.event.issue.number }} to get the release PR's number
      • Use ${{ github.triggering_actor }} to get the current user ENSURE not empty string
      • Use gh api \ "/repos/${{ github.repository_owner }}/${{ github.repository }}/collaborators?permission=admin" --paginate --jq ".[].login" \ | grep -q "$triggering_actor" to get the list of admins
      • Using the gh CLI, we can hit the API endpoint for our repo, listing collaborators with the permission "admin"
      • The paginate flag will fetch until we've gotten all results
      • Use the jq flag to get just the username out of the JSON
      • grep will exit 1 or 0 for finding a match or not
      • Check the exit code with bash if/else
      • When workflow dispatch triggers the workflow
      • Use ternaries and if conditions on steps as needed to reuse the same workflow
      • Skip admin checking, and ensure the releasePr is set correctly before running the action

            Assignee:
            neal.beeken@mongodb.com Neal Beeken
            Reporter:
            neal.beeken@mongodb.com Neal Beeken
            Warren James
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved: