Search Options

Results per page
Sort
Preferred Languages
Advance

Results 1 - 2 of 2 for Kasper (0.18 sec)

  1. build-logic/binary-compatibility/src/main/groovy/gradlebuild/binarycompatibility/rules/AbstractGradleViolationRule.groovy

                    <p>
                    If change was made on the `release` branch but hasn't yet been merged to `master`, merge `release` to `master`:
                    <a class="btn btn-info" role="button" data-toggle="collapse" href="#merge-release-${changeId}" aria-expanded="false" aria-controls="collapseExample">Merge release to master</a>
                    <div class="collapse" id="merge-release-${changeId}">
                      <div class="well">
    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)
  2. .github/workflows/CheckBadMerge.groovy

     *
     * When merging `releaseX` branch into `master`, we should only use the release note from the `master` branch,
     * but sometimes changes on release notes.md was brought to master and merged unnoticed,
     * e.g https://github.com/gradle/gradle/pull/25825
     *
     * This script is to check if there is any merge commit that brings changes from release branch to master.
     * Usage: groovy CheckBadMerge.groovy <commit1> <commit2> ...
    Groovy
    - Registered: Wed May 01 11:36:15 GMT 2024
    - Last Modified: Tue Dec 19 10:35:44 GMT 2023
    - 6.5K bytes
    - Viewed (0)
Back to top