snippets.yml

name: Weekly Team Snippets
on:
  schedule:
    - cron: 10 22 * * 2

jobs:
  create_issue:
    name: Create team sync issue
    runs-on: ubuntu-latest
    permissions:
      issues: write
    steps:
      - name: Create team sync issue
        run: |
  if [[ $CLOSE_PREVIOUS == true ]]; then
    previous_issue_number=$(gh issue list \
      --label "$LABELS" \
      --json number \
      --jq '.[0].number' || echo "")
    if [[ -n $previous_issue_number && $previous_issue_number != "null" ]]; then
      gh issue close "$previous_issue_number"
      gh issue unpin "$previous_issue_number"
    fi
  fi
  new_issue_url=$(gh issue create \
    --title "$TITLE" \
    --assignee "$ASSIGNEES" \
    --label "$LABELS" \
    --body "$BODY")
  if [[ $PINNED == true ]]; then
    gh issue pin "$new_issue_url"
  fi
          fi
        env:
          GH_TOKEN: ${{ secrets.GITHUB_TOKEN }}
          GH_REPO: ${{ github.repository }}
          TITLE: Weekly Snippets
          ASSIGNEES: camihmerhar
          LABELS: snippets
          BODY: |
                ## Process
                - Copy the template format below and comment in the issue
                - Only fill in relevant information 
                - **You don't need something for every category - you may not have anything to report for some weeks**

                Please check of your name below when you have added your snippets or acknowledge that you don't have anything to report for the week:

                - [ ] @camihmerhar

              ## How to Write Program Snippets
              - Bullets should speak to impact and results.
              - Bullets should include relevant links.
              - Bullets, if risks, should include any blockers and asks for help.
              - It is expected that your snippet is submitted Tuesday by noon Eastern each week.

              [If you need help, please read this guideline on how to write strong snippets](https://docs.google.com/document/d/1BSw2lpUsdOmW5crZ7JdRNdRPkXTH-utHF0-mTBDFwJk/edit#).

              ## Template

              Copy the format below and comment in the issue.

              ```
              ## Key Decisions 🔑

              - General guidance is to limit this section to the key decisions you made over the last week (2-3 bullets).

              ## Key Ships 🚀

              - General guidance is to share key ships from the last week (2-3 bullets).

              ## Metrics/Insights 👁

              - General guidance is to share key metrics or insights from the last week (2-3 bullets).

              ## Topics for CSLT Discussion 🗨️  
              - General guidance is to flag areas of risk in the business or topics for discussion amongst CSLT (2-3 bullets).
              - Please note if you need the CSLT to make a decision in Thursday's CSLT session.

              ## Items for RLT/LT Discussion or Decision 🛑
              - General guidance is to flag areas of risk in the business or topics for discussion amongst RLT or LT.
              - Please note if you need the team to make a decision on a topic in Monday's RLT session.
              - Include the @mention of the RLT or LT (Thomas and Directs) the area of focus is targeting and include a deadline by when an update is needed.

              ## 🎉 CELEBRATIONS  
              - What's worth celebrating this week?

              ## More Updates 👇
              - We would like to link back so readers of CS Discussions can drill down for deeper insight. Please add the link to your team's issue/discussion here, if you have one.
              - Add any updates that might not fit into the 2-3 bullets limit per section above.

              ```

          PINNED: false
          CLOSE_PREVIOUS: false