- Sort Score
- Result 10 results
- Languages All
Results 1 - 10 of 10 for Every (0.12 sec)
-
.github/ISSUE_TEMPLATE/20_contributor_feature_request.yml
labels: [ "a:feature", "to-triage" ] assignees: [ ] body: - type: markdown attributes: value: | Please follow the instructions below. We receive dozens of issues every week, so to stay productive, we will close issues that don't provide enough information. Please open Android-related issues on [the Android Issue Tracker](https://source.android.com/source/report-bugs)
Others - Registered: Wed May 08 11:36:15 GMT 2024 - Last Modified: Thu Apr 06 11:10:39 GMT 2023 - 1.5K bytes - Viewed (0) -
.github/DISCUSSION_TEMPLATE/questions.yml
labels: [question] body: - type: markdown attributes: value: | Thanks for your interest in FastAPI! 🚀 Please follow these instructions, fill every question, and do every step. 🙏 I'm asking this because answering questions and solving problems in GitHub is what consumes most of the time.
Others - Registered: Sun May 05 07:19:11 GMT 2024 - Last Modified: Thu Aug 03 15:59:41 GMT 2023 - 5.8K bytes - Viewed (1) -
.github/workflows/test.yml
name: Test on: push: branches: - master pull_request: types: - opened - synchronize schedule: # cron every week on monday - cron: "0 0 * * 1" jobs: lint: runs-on: ubuntu-latest steps: - name: Dump GitHub context env: GITHUB_CONTEXT: ${{ toJson(github) }} run: echo "$GITHUB_CONTEXT" - uses: actions/checkout@v4
Others - Registered: Sun May 05 07:19:11 GMT 2024 - Last Modified: Thu Apr 18 19:40:57 GMT 2024 - 4.4K bytes - Viewed (2) -
.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) -
.github/ISSUE_TEMPLATE/10_contributor_bug_report.yml
description: Create a report to help us improve labels: [ "a:bug", "to-triage" ] assignees: [ ] body: - type: markdown attributes: value: | Please follow the instructions below. We receive dozens of issues every week, so to stay productive, we will close issues that don't provide enough information. If you need help with Gradle or have a usage question, please reach [our community](http://help.gradle.org/) instead of creating an issue.
Others - Registered: Wed May 08 11:36:15 GMT 2024 - Last Modified: Fri Feb 16 07:49:32 GMT 2024 - 3K bytes - Viewed (0) -
.github/ISSUE_TEMPLATE/11-language-change.yml
- type: textarea id: cost-description attributes: label: "Cost Description" description: "What is the cost of this proposal? (Every language change has a cost)" - type: input id: go-toolchain attributes: label: Changes to Go ToolChain
Others - Registered: Tue May 07 11:14:38 GMT 2024 - Last Modified: Wed Nov 22 20:49:24 GMT 2023 - 4.7K bytes - Viewed (0) -
.github/workflows/stale-pr.yml
name: 'Close stale PRs' on: schedule: # Execute every hour at xx:05 to avoid conflicts with other workflows - cron: '5 * * * *' permissions: {} jobs: stale: permissions: pull-requests: write runs-on: ubuntu-latest steps: - uses: actions/stale@v9 with: operations-per-run: 50 ascending: true exempt-all-milestones: true
Others - Registered: Wed May 08 11:36:15 GMT 2024 - Last Modified: Thu May 02 09:13:16 GMT 2024 - 1.7K bytes - Viewed (0) -
.github/workflows/feedback.yml
name: Feedback on: schedule: - cron: '0 * * * *' # every hour workflow_dispatch: permissions: {} jobs: feedback: permissions: issues: write pull-requests: write runs-on: ubuntu-latest steps: # Feedback loop: ask for something on PR/Issue and close if not provided or return to the queue on update. # https://github.com/gradle/issue-management-action/blob/main/src/feedback.ts
Others - Registered: Wed May 08 11:36:15 GMT 2024 - Last Modified: Thu May 02 09:13:16 GMT 2024 - 516 bytes - Viewed (0) -
.github/ISSUE_TEMPLATE/00-bug.yml
attributes: label: "What did you see happen?" description: Command invocations and their associated output, functions with their arguments and return results, full stacktraces for panics (upload a file if it is very long), etc. Prefer copying text output over using screenshots. validations: required: true - type: textarea id: expected-behavior attributes: label: "What did you expect to see?"
Others - Registered: Tue May 07 11:14:38 GMT 2024 - Last Modified: Thu Jan 04 23:31:17 GMT 2024 - 3.3K bytes - Viewed (0) -
.github/ISSUE_TEMPLATE/feature_addition_request.yaml
- type: markdown attributes: value: > Comparing two approaches to a use case side by side can make it easier to examine the differences between them. Additionally, it's very useful to us if you can provide a "straw API" — what the method signatures would look like, for example, even if the method and class names are still
Others - Registered: Fri May 03 12:43:13 GMT 2024 - Last Modified: Fri Nov 17 18:47:47 GMT 2023 - 5.8K bytes - Viewed (0)