Search Options

Results per page
Sort
Preferred Languages
Advance

Results 1 - 10 of 13 for Team (0.13 sec)

  1. .github/workflows/team-triage-stale.yml

    name: 'Requeue stale team-triage items'
    on:
      schedule:
        # Execute every day at 00:05 to avoid conflicts with other workflows
        - cron: '5 0 * * *'
    
    permissions: {}
    
    jobs:
      requeue:
        permissions:
          issues: write
          pull-requests: write
        runs-on: ubuntu-latest
        steps:
          - uses: actions/stale@v9
            with:
              operations-per-run: 50
              remove-stale-when-updated: false
    
    Others
    - Registered: Wed May 08 11:36:15 GMT 2024
    - Last Modified: Thu May 02 09:13:16 GMT 2024
    - 835 bytes
    - Viewed (0)
  2. .github/workflows/slack-notifier.yml

    name: IDE Experience team notifier
    run-name: Notify the IDE Experience team about relevant issues
    on:
      issues:
        types:
          - labeled
    
    permissions: {}
    
    jobs:
      send-slack-notification:
        if: ${{ github.event.label.name == 'in:ide' || github.event.label.name == 'in:eclipse-plugin' || github.event.label.name == 'in:idea-plugin' || github.event.label.name == 'in:tooling-api' }}
        runs-on: ubuntu-latest
        steps:
    Others
    - Registered: Wed May 08 11:36:15 GMT 2024
    - Last Modified: Thu May 02 09:13:16 GMT 2024
    - 1.3K bytes
    - Viewed (0)
  3. .github/workflows/notify-on-rc-for-manual-test.yml

    name: IDE Experience team notifier
    run-name: Notify the IDE Experience team about new RCs for manual testing
    on:
      push:
        tags:
          - 'v*.*.*-RC1'
    
    permissions: {}
    
    jobs:
      send-slack-notification:
        runs-on: ubuntu-latest
        steps:
          - name: Send Slack notification about new RCs for manual testing
            id: slack
            uses: slackapi/slack-github-action@v1.23.0
            with:
              payload: |
                {
    Others
    - Registered: Wed May 08 11:36:15 GMT 2024
    - Last Modified: Thu May 02 09:13:16 GMT 2024
    - 1K bytes
    - Viewed (0)
  4. architecture/README.md

    This directory contains documentation that describes Gradle's architecture and how the various pieces fit together and work.
    
    ## Architecture decision records (ADRs)
    
    The Gradle team uses ADRs to record architectural decisions that the team has made.
    
    See [Architecture decisions records](standards) for the list of ADRs.
    Plain Text
    - Registered: Wed May 08 11:36:15 GMT 2024
    - Last Modified: Thu May 02 06:42:46 GMT 2024
    - 2.4K bytes
    - Viewed (0)
  5. .github/PULL_REQUEST_TEMPLATE.md

    - [ ] Check ["Allow edit from maintainers" option](https://help.github.com/articles/allowing-changes-to-a-pull-request-branch-created-from-a-fork/) in pull request so that additional changes can be pushed by Gradle team.
    - [ ] Provide integration tests (under `<subproject>/src/integTest`) to verify changes from a user perspective.
    - [ ] Provide unit tests (under `<subproject>/src/test`) to verify logic.
    Plain Text
    - Registered: Wed May 08 11:36:15 GMT 2024
    - Last Modified: Tue Feb 13 22:36:19 GMT 2024
    - 1.7K bytes
    - Viewed (0)
  6. architecture-standards/0001-use-architectural-decision-records.md

    * Review in Google Doc is not as simple as a PR code review in GitHub
    
    ## Decision
    
    The *Build Tool Team* has decided to use Architectural Decision Records (aka ADR) to track decisions we want to follow.
    
    The main logic with ADRs is to describe (architectural) decisions made:
    
    * To provide best practices and solutions we (as *build tool* team) want to promote.
    * To avoid asking the same thing multiple times during code review.
    Plain Text
    - Registered: Wed Feb 14 11:36:15 GMT 2024
    - Last Modified: Wed Feb 07 00:43:19 GMT 2024
    - 2.8K bytes
    - Viewed (0)
  7. architecture/standards/0001-use-architectural-decision-records.md

    * Review in Google Docs is not as simple as a PR code review in GitHub
    
    ## Decision
    
    The *Build Tool Team* has decided to use Architectural Decision Records (aka ADR) to track decisions we want to follow.
    
    The main logic with ADRs is to describe (architectural) decisions made:
    
    * To provide best practices and solutions we (as the *build tool* team) want to promote.
    * To avoid asking the same thing multiple times during code review.
    Plain Text
    - Registered: Wed May 08 11:36:15 GMT 2024
    - Last Modified: Sat Mar 02 21:54:40 GMT 2024
    - 2.8K bytes
    - Viewed (0)
  8. .cm/plugins/filters/isEnabledUser/index.js

    /**
     * @module isEnabledUser
     * @description Returns true if the username that is passed to this function is a member of the Gradle BT Team who has opted into gitStream automations.
     * @param {string} Input - The GitHub username to check.
     * @returns {boolean} Returns true if the user is specified in any of the lists of Gradle BT team members above, otherwise false.
     * @example {{ pr.author | isEnabledUser }}
     */
    function isEnabledUser(username) {
    JavaScript
    - Registered: Wed Apr 17 11:36:08 GMT 2024
    - Last Modified: Mon Feb 05 22:00:34 GMT 2024
    - 923 bytes
    - Viewed (0)
  9. architecture/standards/0004-use-a-platform-architecture.md

    An architecture module is responsible for providing a coherent set of features and:
    
    - Provides a set of APIs and services for use from outside the module.
    - Has a private implementation.
    - Is owned by a single team. A team may own multiple architecture modules.
    
    The modules are arranged into several different "Gradle platforms".
    A Gradle platform is a logical distribution that provides support for a specific kind of automation.
    Plain Text
    - Registered: Wed May 08 11:36:15 GMT 2024
    - Last Modified: Sun Feb 25 22:19:29 GMT 2024
    - 4.5K bytes
    - Viewed (0)
  10. build-logic-commons/gradle-plugin/src/main/kotlin/gradlebuild.ci-reporting.gradle.kts

     * failing tasks only, to not use up unnecessary disk space on Team City. This also improves the performance of
     * artifact publishing by reducing the artifacts and packaging reports that consist of multiple files.
     *
     * Reducing the number of reports also makes it easier to find the important ones when analysing a failed build in
     * Team City.
     */
    
    Plain Text
    - Registered: Wed May 01 11:36:15 GMT 2024
    - Last Modified: Tue Jul 11 06:57:51 GMT 2023
    - 2K bytes
    - Viewed (0)
Back to top