on:
  issues:
    types:
      - labeled

permissions: {}

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:
      - name: Send Slack notification about issues with specific labels
        id: slack

     * This means that every line in the merge commit version should be either:
     * - Only exists on `master`.
     * - Exists on `master` and `releaseX`.
     * If any line is only present on `releaseX` version, then it's a bad file.
     * Also, we ignore empty lines.
     */
    static boolean isBadFileInMergeCommit(String filePath, String mergeCommit, String masterCommit, String releaseCommit) {
        try {

            return@collectDescendantsOfType false
        }

        // Parameter type check
        method.parameterTypes
            .asSequence()
            // Drop the receiver if present
            .drop(if (extensionCandidate) 1 else 0)
            .withIndex()
            .all<IndexedValue<CtClass>> {
                val ktParamType = ktFunction.valueParameters[it.index].typeReference!!

4. Validate your changes before committing.\
Run the `./gradlew sanityCheck` task again to make sure there are no more errors.

#### Filtering changes by severity

There is a somewhat non-obvious filter present on the page that allows you to control which type of messages are displayed.
The filter is a dropdown box that appears when you click the `Severity ⬇️ ` label in the black header bar to the immediate right of the Gradle version.

        args:
          label: "⚠️ Includes TODOs"
          color: {{ colors.yellow }}
      - action: add-comment@v1
        args:
          comment: |
            :warning: 'There are new TODOs present in this change.  Should any be removed?'

# To simplify the automations section, some calculations are placed under unique YAML keys defined here.

In a distributed team with many subteams, the best solution to communicate decisions is to use a format accessible by everyone in charge of development.

We use *Specification* and *Discovery* documents stored in Google Drive, but they present some downsides:

* They are rarely updated after creation and initial review, and then become hard to follow, especially after important decisions are made

          label: "⚠️ Missing Javadoc"
          color: {{ colors.yellow }}
      - action: add-comment@v1
        args:
          comment: |
            :warning: This PR creates new top-level Java classes, but has no Javadoc present. Please document all top-level classes with Javadoc.

is:
  java: {{ files | extensions | match(term='java') | every }}
  new: {{ source.diff.files | map(attr='original_file') | match(regex=r/^$/) | some }}

colors: