on:
  schedule:
    # Execute every day at 00:05 to avoid conflicts with other workflows
    - cron: '5 0 * * *'

permissions:
  issues: write
  pull-requests: write

jobs:
  requeue:
    runs-on: ubuntu-latest
    steps:
      - uses: actions/stale@v9
        with:
          operations-per-run: 50
          remove-stale-when-updated: false

          only-issue-labels: ':wave: team-triage'

name: IDE Experience team notifier
run-name: Notify the IDE Experience team about new RCs for manual testing
on:
  push:
    tags:
      - 'v*.*.*-RC1'

jobs:
  send-slack-notification:
    runs-on: ubuntu-latest
    steps:
      - name: Send Slack notification about new RCs for manual testing
        id: slack
        uses: slackapi/slack-github-action@v1.23.0
        with:
          payload: |
            {

            Please report it to @gradle/bt-support team
          days-before-issue-close: -1
          close-issue-message: >
            **BUG!** This issue should not be closed by the "stale" workflow.
            Please report it to @gradle/bt-support team
          close-issue-reason: not_planned

          # PULL REQUESTS -----------------------------------------------------

      value: >
        Filing feature requests is one of the most popular ways to contribute to Guava.


        Be aware, though: most feature requests are not accepted, even if they're suggested by
        a full-time Guava team member. [Feedback](https://stackoverflow.com/a/4543114) from our
        users indicates that they really appreciate Guava's high power-to-weight ratio. It's

name: IDE Experience team notifier
run-name: Notify the IDE Experience team about relevant issues
on:
  issues:
    types:
      - labeled

jobs:
  send-slack-notification:
    if: ${{ github.event.label.name == 'in:ide' || github.event.label.name == 'in:eclipse-plugin' || github.event.label.name == 'in:idea-plugin' || github.event.label.name == 'in:tooling-api' }}
    runs-on: ubuntu-latest
    steps:

      value: >
        Filing feature requests is one of the most popular ways to contribute to Guava.


        Be aware, though: most feature requests are not accepted, even if they're suggested by
        a full-time Guava team member. [Feedback](https://stackoverflow.com/a/4543114) from our
        users indicates that they really appreciate Guava's high power-to-weight ratio. It's

    author_link: https://www.linkedin.com/in/mnrozhkov/
    link: https://www.evidentlyai.com/blog/fastapi-tutorial
    title: ML serving and monitoring with FastAPI and Evidently
  - author: Visual Studio Code Team
    author_link: https://code.visualstudio.com/
    link: https://code.visualstudio.com/docs/python/tutorial-fastapi
    title: FastAPI Tutorial in Visual Studio Code
  - author: Apitally
    author_link: https://apitally.io

and variants of Istio. - Better security: separate Istio components reside in different namespaces, allowing different teams or roles to manage different parts of Istio. For example, a security team would maintain the root CA and policy, a telemetry team may only have access to Prometheus, and a different team may maintain the control plane components (which are highly security sensitive). The install is organized in 'environments' - each environment consists of a set of components in different namespaces...

df.leg.br dgca.aero dh.bytemark.co.uk dhl diadem.cloud diamonds dielddanuorri.no diet digick.jp digital dinosaur.museum direct direct.quickconnect.cn direct.quickconnect.to directory discordsays.com discordsez.com discount discourse.group discourse.team discover discovery.museum dish diskstation.eu diskstation.me diskstation.org diskussionsbereich.de ditchyourip.com divtasvuodna.no divttasvuotna.no diy dj dk dk.eu.org dlugoleka.pl dm dn.ua dnepropetrovsk.ua dni.us dnipropetrovsk.ua dnp dnsalias.com...