```sh
$ cd minio
$ git remote add upstream https://github.com/minio/minio
$ git fetch upstream
$ git merge upstream/master
...
```

### Create your feature branch

Before making code changes, make sure you create a separate branch for these changes

```
git checkout -b my-new-feature
```

### Test MinIO server changes

After your code changes, make sure

based on a specific branch. Currently, we have two pipelines: `master` and `release`, but you can easily create
and test another isolated pipeline from any branch. 

We'll explain everything via an example. Let's say you make some changes on your branch `myTestBranch`
(we highly recommend to name this branch without prefix and hyphen (`-`) because it's used to generate build type ID) and want to

package promotion

import common.VersionedSettingsBranch
import vcsroots.gradlePromotionBranches

class PublishNightlySnapshotFromQuickFeedbackStepUpload(branch: VersionedSettingsBranch) : BasePublishGradleDistribution(
    promotedBranch = branch.branchName,
    prepTask = branch.prepNightlyTaskName(),
    triggerName = "QuickFeedback",
    vcsRootId = gradlePromotionBranches
) {
    init {

          projectName: fastapitiangolo
          directory: './site'
          gitHubToken: ${{ secrets.GITHUB_TOKEN }}
          branch: ${{ ( github.event.workflow_run.head_repository.full_name == github.repository && github.event.workflow_run.head_branch == 'master' && 'main' ) || ( github.event.workflow_run.head_sha ) }}
      - name: Comment Deploy
        if: steps.deploy.outputs.url != ''

    run:
      - action: add-comment@v1
        args:
          comment: |
            {{ by_platform_comment }}

by_platform_comment: |

        publishBuildStatusToGithub(model)
    }

    triggers.vcs {
        quietPeriodMode = VcsTrigger.QuietPeriodMode.DO_NOT_USE
        branchFilter = """
+:gh-readonly-queue/${model.branch.branchName}/*
+:${model.branch.branchName}
"""
    }

    dependencies {
        snapshot(RelativeId(stageTriggerId(model, StageName.READY_FOR_NIGHTLY))) {
            onDependencyFailure = FailureAction.FAIL_TO_START

main channel of communication for contributors.  
There are some guidelines which will make applying PRs easier for us:
+ Create a topic branch from where you want to base your work (this is usually the master branch).
  Push your changes to a topic branch in your fork of the repository.
+ Make commits of logical units.
+ Respect the original code style: by using the same [codestyle][code-style],

name: Set nightly branch to master HEAD

permissions: {}

jobs:
  master-to-nightly:
    if: github.repository == 'tensorflow/tensorflow' # Don't do this in forks
    runs-on: ubuntu-latest
    permissions:
      contents: write
    steps:
    - uses: zofrex/mirror-branch@a8809f0b42f9dfe9b2c5c2162a46327c23d15266 # v1.0.3
      name: Set nightly branch to master HEAD
      with:

                  <div class="well">
                      Sometimes, the change was made on the `release` branch but hasn't yet been published to the baseline version.
                      In that case, you can publish a new snapshot from the release branch. This will update `released-versions.json` on `master`.

          ]
        },
        "french_analyzer": {
          "type": "custom",
          "tokenizer": "standard",
          "filter": [
            "truncate20_filter",
            "french_elision",
            "lowercase",
            "french_stop",
            "french_keywords",
            "french_override",
            "french_stemmer"
          ]
        },