Search Options

Results per page
Sort
Preferred Languages
Advance

Results 1 - 10 of 18 for mime (0.13 sec)

  1. .cm/lacks_tests.cm

    # the conditions on each line).  Each condition is specified as a Jinja expression.  You
    # can also use the constant `true` if you want to always run the actions.
    
    # Each automation is independent of the others.  Every time one of the `on` conditions match for
    # this PR, this automations will have its `if` checked to run.  In a way, the `on` conditions
    # function as an implicit first `if` for every automation in the file.
    
    Plain Text
    - Registered: Wed May 08 11:36:15 GMT 2024
    - Last Modified: Fri Apr 12 13:42:16 GMT 2024
    - 2.4K bytes
    - Viewed (0)
  2. .teamcity/test-buckets.json

    					"name":"TestDistribution"
    				},
    				"subprojects":[
    					"core"
    				]
    			},
    			{
    				"parallelizationMethod":{
    					"name":"TestDistribution"
    				},
    				"subprojects":[
    					"launcher",
    					"time",
    					"logging-api",
    					"kotlin-dsl-plugins",
    					"serialization",
    					"toolchains-jvm-shared",
    					"docs-asciidoctor-extensions-base",
    					"internal-instrumentation-processor",
    					"security",
    Json
    - Registered: Wed May 08 11:36:15 GMT 2024
    - Last Modified: Mon May 06 14:29:38 GMT 2024
    - 49.9K bytes
    - Viewed (0)
  3. .cm/add_usual_expert.cm

    # the conditions on each line).  Each condition is specified as a Jinja expression.  You
    # can also use the constant `true` if you want to always run the actions.
    
    # Each automation is independent of the others.  Every time one of the `on` conditions match for
    # this PR, this automations will have its `if` checked to run.  In a way, the `on` conditions
    # function as an implicit first `if` for every automation in the file.
    
    Plain Text
    - Registered: Wed May 08 11:36:15 GMT 2024
    - Last Modified: Fri Apr 12 13:42:16 GMT 2024
    - 1.4K bytes
    - Viewed (0)
  4. .cm/complex_changes.cm

    # the conditions on each line).  Each condition is specified as a Jinja expression.  You
    # can also use the constant `true` if you want to always run the actions.
    
    # Each automation is independent of the others.  Every time one of the `on` conditions match for
    # this PR, this automations will have its `if` checked to run.  In a way, the `on` conditions
    # function as an implicit first `if` for every automation in the file.
    
    Plain Text
    - Registered: Wed May 08 11:36:15 GMT 2024
    - Last Modified: Fri Apr 12 13:42:16 GMT 2024
    - 1.7K bytes
    - Viewed (0)
  5. build-logic/dependency-modules/src/main/kotlin/gradlebuild/modules/extension/ExternalModulesExtension.kt

        val jetbrainsAnnotations = "org.jetbrains:annotations"
        val jgit = "org.eclipse.jgit:org.eclipse.jgit"
        val jgitSsh = "org.eclipse.jgit:org.eclipse.jgit.ssh.apache"
        val joda = "joda-time:joda-time"
        val jsch = "com.github.mwiede:jsch"
        val jsr305 = "com.google.code.findbugs:jsr305"
        val julToSlf4j = "org.slf4j:jul-to-slf4j"
        val junit = "junit:junit"
    Plain Text
    - Registered: Wed May 01 11:36:15 GMT 2024
    - Last Modified: Tue Apr 16 15:50:58 GMT 2024
    - 14.4K bytes
    - Viewed (0)
  6. .cm/estimated_time_to_review.cm

    on:
      - pr_created
      - commit
      - comment_added
    
    automations:
    
      # Add a label that indicates how many minutes it will take to review the PR and categorizes it
      estimated_time_to_review:
        if:
          - {{ ('estimated_time_to_review' | isEnabledAutomation(pr)) }}
        run:
          - action: add-label@v1
            # etr is defined in the last section of this example
            args:
              label: "{{ calc.etr }} min review"
    Plain Text
    - Registered: Wed May 08 11:36:15 GMT 2024
    - Last Modified: Fri Apr 12 13:42:16 GMT 2024
    - 2K bytes
    - Viewed (0)
  7. .teamcity/src/main/kotlin/promotion/BasePromotionBuildType.kt

                // https://blog.jetbrains.com/teamcity/2013/05/explaining-the-shared-resources-plugin/
                // we only allow 1 promotion job running at the same time to avoid website xml conflicts
                feature {
                    type = "JetBrains.SharedResources"
                    param("locks-param", "WebsiteReleasesXml writeLock")
                }
            }
        }
    Plain Text
    - Registered: Wed May 08 11:36:15 GMT 2024
    - Last Modified: Wed Apr 24 03:34:53 GMT 2024
    - 2.1K bytes
    - Viewed (0)
  8. .cm/platform_labels.cm

    # the conditions on each line).  Each condition is specified as a Jinja expression.  You
    # can also use the constant `true` if you want to always run the actions.
    
    # Each automation is independent of the others.  Every time one of the `on` conditions match for
    # this PR, this automations will have its `if` checked to run.  In a way, the `on` conditions
    # function as an implicit first `if` for every automation in the file.
    
    Plain Text
    - Registered: Wed May 08 11:36:15 GMT 2024
    - Last Modified: Mon Apr 22 15:32:31 GMT 2024
    - 2.5K bytes
    - Viewed (0)
  9. .cm/misc_labels.cm

    # the conditions on each line).  Each condition is specified as a Jinja expression.  You
    # can also use the constant `true` if you want to always run the actions.
    
    # Each automation is independent of the others.  Every time one of the `on` conditions match for
    # this PR, this automations will have its `if` checked to run.  In a way, the `on` conditions
    # function as an implicit first `if` for every automation in the file.
    
    Plain Text
    - Registered: Wed May 08 11:36:15 GMT 2024
    - Last Modified: Fri Apr 12 13:42:16 GMT 2024
    - 3K bytes
    - Viewed (0)
  10. build-logic/binary-compatibility/src/main/groovy/gradlebuild/binarycompatibility/rules/AbstractGradleViolationRule.groovy

                    <div class="collapse" id="merge-release-${changeId}">
                      <div class="well">
                          Merging `release` back to `master` is a regular operation you’re free to do, at any time. Usually, you will see conflicts in `notes.md` or `accepted-public-api-changes.json`.
                          On `master` branch, these two files are usually reset (cleaned up), unless you have special reasons not to do so.
    Groovy
    - Registered: Wed May 01 11:36:15 GMT 2024
    - Last Modified: Tue Apr 23 08:40:36 GMT 2024
    - 10.4K bytes
    - Viewed (0)
Back to top