Skip to content

Decision: Should the logged-out "skip to dashboard" take users to the Hosting flow? #423649

Decision: Should the logged-out "skip to dashboard" take users to the Hosting flow?

Decision: Should the logged-out "skip to dashboard" take users to the Hosting flow? #423649

Workflow file for this run

name: Repo gardening
on:
pull_request_target: # When a PR is opened, edited, updated, closed, or a label is added.
types: [opened, reopened, synchronize, edited, labeled, closed]
issues: # For auto-triage of issues.
types: [opened, labeled, reopened, edited, closed]
issue_comment: # To gather support references in issue comments.
types: [created]
concurrency:
# For pull_request_target, cancel any concurrent jobs with the same type (e.g. "opened", "labeled") and branch.
# Don't cancel any for other events, accomplished by grouping on the unique run_id.
group: gardening-${{ github.event_name }}-${{ github.event.action }}-${{ github.event_name == 'pull_request_target' && github.event.pull_request.head.ref || github.run_id }}
cancel-in-progress: true
jobs:
repo-gardening:
name: 'Assign issues, Clean up labels, and notify Design and Editorial when necessary'
runs-on: ubuntu-latest
if: github.event_name == 'pull_request_target' || github.event.pull_request.head.repo.full_name == github.event.pull_request.base.repo.full_name
timeout-minutes: 20 # 2024-07-02 -- Bumping from 10 to 20 minutes to allow for more time to process issues and PRs. The update softprops/turnstyle@v2 seems to have slowed things down.
steps:
- name: Checkout
uses: actions/checkout@v3
- name: Setup Node
uses: actions/setup-node@v3
with:
node-version-file: '.nvmrc'
- name: Wait for prior instances of the workflow to finish
uses: softprops/turnstyle@v2
env:
GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
- name: 'Run gardening action'
uses: automattic/action-repo-gardening@trunk
with:
github_token: ${{ secrets.GITHUB_TOKEN }}
slack_token: ${{ secrets.SLACK_TOKEN }}
slack_design_channel: ${{ secrets.SLACK_DESIGN_CHANNEL }}
slack_editorial_channel: ${{ secrets.SLACK_EDITORIAL_CHANNEL }}
slack_team_channel: ${{ secrets.SLACK_TEAM_CHANNEL }}
slack_he_triage_channel: ${{ secrets.SLACK_HE_TRIAGE_CHANNEL }}
slack_quality_channel: ${{ secrets.SLACK_QUALITY_CHANNEL }}
triage_projects_token: ${{ secrets.PROJECT_AUTOMATION_TOKEN }}
project_board_url: ${{ secrets.PROJECT_BOARD_URL }}
openai_api_key: ${{ secrets.OPENAI_API_KEY }}
tasks: 'assignIssues,cleanLabels,notifyDesign,notifyEditorial,flagOss,triageIssues,gatherSupportReferences,replyToCustomersReminder,updateBoard'