Search Options

Results per page
Sort
Preferred Languages
Advance

Results 1 - 10 of 461 for changes (0.05 sec)

  1. .github/workflows/latest-changes.yml

    name: Latest Changes
    
    on:
      pull_request_target:
        branches:
          - master
        types:
          - closed
      workflow_dispatch:
        inputs:
          number:
            description: PR number
            required: true
          debug_enabled:
            description: 'Run the build with tmate debugging enabled (https://github.com/marketplace/actions/debugging-with-tmate)'
            required: false
            default: 'false'
    
    jobs:
      latest-changes:
    Registered: Sun Nov 03 07:19:11 UTC 2024
    - Last Modified: Mon Aug 26 02:14:56 UTC 2024
    - 1.3K bytes
    - Viewed (0)
  2. CONTRIBUTING.md

    2. Accept the changes.\
    If you are sure that the changes are intentional, follow the steps described in the report.
    This includes adding the description of the changes to the `accepted-public-api-changes.json` file, and providing a reason for each change.
    You can add the changes to any place in the file, e.g. at the top.
    
    3. Make sure the file with accepted changes is sorted.\
    Registered: Wed Nov 06 11:36:14 UTC 2024
    - Last Modified: Tue Nov 05 15:15:33 UTC 2024
    - 15.6K bytes
    - Viewed (0)
  3. docs/en/docs/management-tasks.md

    So, having a nice PR title will not only look nice in GitHub, but also in the release notes. 📝
    
    ## Add Labels to PRs
    
    Registered: Sun Nov 03 07:19:11 UTC 2024
    - Last Modified: Fri Aug 16 21:56:33 UTC 2024
    - 14.2K bytes
    - Viewed (0)
  4. RELEASE_BRANCHES.md

    One week before a release, the release branch goes into a state of code freeze. At this point only critical release
    blocking bugs are addressed. Additional changes that are targeted for new features and capabilities will not be merged.
    
    ## Features requiring API changes
    
    If a PR change requires an API change
    * Updates to documentation do not require explicit approval from the Technical Oversight Committee (TOC). This can be
    Registered: Wed Nov 06 22:53:10 UTC 2024
    - Last Modified: Mon Sep 16 21:14:17 UTC 2024
    - 4.2K bytes
    - Viewed (0)
  5. build-logic/binary-compatibility/src/main/groovy/gradlebuild/binarycompatibility/rules/AbstractGradleViolationRule.groovy

                seenApiChanges.add(change)
                return Violation.accept(member, "${rejection.getHumanExplanation()}. Reason for accepting this: <b>Upgraded property</b>")
            }
    
            def acceptanceJson = new AcceptedApiChange(
                change.type,
                change.member,
                '[ADD YOUR CUSTOM REASON HERE]',
                change.changes
            )
    
    Registered: Wed Nov 06 11:36:14 UTC 2024
    - Last Modified: Mon Aug 19 15:30:48 UTC 2024
    - 10.4K bytes
    - Viewed (0)
  6. manifests/charts/UPDATING-CHARTS.md

    - If `values.yaml` is changed, be sure to update corresponding values changes in [../profiles/default.yaml](../profiles/default.yaml)
    
    ### Step 3. Update istioctl schema
    
    Istioctl uses a [schema](../../operator/pkg/apis/values_types.proto) to validate the values. Any changes to
    the schema must be added here, otherwise istioctl users will see errors.
    Registered: Wed Nov 06 22:53:10 UTC 2024
    - Last Modified: Thu Aug 15 16:31:46 UTC 2024
    - 4.8K bytes
    - Viewed (0)
  7. CONTRIBUTING.md

        changes to be made to PR to pass quality checks and send it back or on a
        rare occasion we may reject it.
    
    **3. Review**
    
    -   For a valid PR, reviewer (person familiar with the code/functionality)
        checks if the PR looks good or needs additional changes.
    -   If all looks good, the reviewer will approve the PR.
    -   If a change is needed, the contributor is requested to make the suggested
    Registered: Tue Nov 05 12:39:12 UTC 2024
    - Last Modified: Wed Oct 23 06:20:12 UTC 2024
    - 15.9K bytes
    - Viewed (0)
  8. docs/en/docs/deployment/versions.md

    FastAPI also follows the convention that any "PATCH" version change is for bug fixes and non-breaking changes.
    
    /// tip
    
    The "PATCH" is the last number, for example, in `0.2.3`, the PATCH version is `3`.
    
    ///
    
    So, you should be able to pin to a version like:
    
    ```txt
    fastapi>=0.45.0,<0.46.0
    ```
    
    Breaking changes and new features are added in "MINOR" versions.
    
    Registered: Sun Nov 03 07:19:11 UTC 2024
    - Last Modified: Sun Aug 25 02:44:06 UTC 2024
    - 3.4K bytes
    - Viewed (0)
  9. .github/release-drafter.yml

          - 'enhancement'
      - title: '🐛 Bug Fixes'
        labels:
          - 'fix'
          - 'bugfix'
          - 'bug'
      - title: '🧰 Maintenance'
        label: 'chore'
    change-template: '- $TITLE @$AUTHOR (#$NUMBER)'
    change-title-escapes: '\<*_&'
    template: |
      ## Changes
    
    Registered: Sun Nov 03 09:35:10 UTC 2024
    - Last Modified: Wed Oct 09 11:31:04 UTC 2024
    - 428 bytes
    - Viewed (0)
  10. docs/en/docs/contributing.md

    During local development, there is a script that builds the site and checks for any changes, live-reloading:
    
    <div class="termy">
    
    ```console
    $ python ./scripts/docs.py live
    
    <span style="color: green;">[INFO]</span> Serving on http://127.0.0.1:8008
    <span style="color: green;">[INFO]</span> Start watching changes
    <span style="color: green;">[INFO]</span> Start detecting changes
    ```
    
    </div>
    
    Registered: Sun Nov 03 07:19:11 UTC 2024
    - Last Modified: Sun Aug 25 02:44:06 UTC 2024
    - 12.7K bytes
    - Viewed (0)
Back to top