jobs:
  main:
    permissions:
      contents: read
      pull-requests: write
    runs-on: ubuntu-latest
    steps:
      - name: Check if PRs have merge conflicts
        uses: eps1lon/actions-label-merge-conflict@v3
        with:
          dirtyLabel: "conflicts"
          repoToken: "${{ secrets.GITHUB_TOKEN }}"

---
- job:
    name: "elastic+elasticsearch+pull-request+packaging-tests-windows"
    display-name: "elastic / elasticsearch - pull request packaging-tests-windows"
    description: "Testing of Elasticsearch pull requests - packaging-tests-windows"
    # We use a hard-coded workspace directory here to avoid hitting windows path length limits
    child-workspace: "C:\\Users\\jenkins\\workspace\\pr-packaging-windows\\${BUILD_NUMBER}"
    project-type: matrix

---
- job:
    name: "elastic+elasticsearch+pull-request+part-1-fips"
    display-name: "elastic / elasticsearch - pull request part-1 fips"
    description: "Testing of Elasticsearch pull requests - part-1 fips"
    workspace: "/dev/shm/elastic+elasticsearch+pull-request+part-1-fips"
    scm:
      - git:
          refspec: "+refs/pull/${ghprbPullId}/*:refs/remotes/origin/pr/${ghprbPullId}/*"
          branches:
            - "${ghprbActualCommit}"

the `Accept-Encoding` header is not otherwise set. Web servers must be configured to return zstd
responses.

Note that zstd is not used for sending requests.

```java
OkHttpClient client = new OkHttpClient.Builder()
  .addInterceptor(CompressionInterceptor(Zstd, Gzip))
  .build();
```

```kotlin
implementation("com.squareup.okhttp3:okhttp-zstd:5.3.0")
```

            }
            return (T) Boolean.valueOf(value.toString());
        }
        return null;
    }

    /**
     * Encodes a URL by encoding non-URL-safe characters.
     * Uses the request's character encoding if available, otherwise defaults to UTF-8.
     * Only encodes characters that are not considered URL-safe according to CharUtil.
     *
     * @param url the URL to encode

---
- job:
    name: "elastic+elasticsearch+pull-request+packaging-tests-unix-sample"
    display-name: "elastic / elasticsearch - pull request packaging-tests-unix-sample"
    description: "Testing of Elasticsearch pull requests - packaging-tests-unix-sample"
    project-type: matrix
    node: master
    scm:
      - git:
          refspec: "+refs/pull/${ghprbPullId}/*:refs/remotes/origin/pr/${ghprbPullId}/*"
          branches:

---
- job:
    name: "elastic+elasticsearch+pull-request+packaging-tests-windows-nojdk"
    display-name: "elastic / elasticsearch - pull request packaging-tests-windows-nojdk"
    description: "Testing of Elasticsearch pull requests - packaging-tests-windows-nojdk"
    # We use a hard-coded workspace directory here to avoid hitting windows path length limits
    child-workspace: "C:\\Users\\jenkins\\workspace\\pr-packaging-windows\\${BUILD_NUMBER}"

1. Click **Management**.
1. Click **Index Patterns**.
1. Click **Create index pattern** button
1. Input "fess\_log\*" to the textbox of **index pattern**.
1. Click **Next step**.
1. Set "requestedAt" to the **Time Filter field name**.
1. Click **Create index pattern**.
1. Click **Saved Objects**.
1. Click **Import** and select "fess\_log.ndjson" to import example settings.
1. Click **Dashboard**.

Uygulamaları deploy ederken, çok çekirdekten (multiple cores) faydalanmak ve daha fazla request'i karşılayabilmek için büyük olasılıkla process replikasyonu (birden fazla process) isteyeceksiniz.

[Daha önceki Deployment Concepts](concepts.md) bölümünde gördüğünüz gibi, kullanabileceğiniz birden fazla strateji var.

name: Label Approved

on:
  schedule:
    - cron: "0 12 * * *"
  workflow_dispatch:

permissions:
  pull-requests: write

jobs:
  label-approved:
    if: github.repository_owner == 'fastapi'
    runs-on: ubuntu-latest
    steps:
    - name: Dump GitHub context
      env:
        GITHUB_CONTEXT: ${{ toJson(github) }}
      run: echo "$GITHUB_CONTEXT"
    - uses: actions/checkout@v6
    - name: Set up Python