|
| 1 | +# These settings are synced to GitHub by https://probot.github.io/apps/settings/ |
| 2 | + |
| 3 | +repository: |
| 4 | + # See https://docs.github.com/en/rest/reference/repos#update-a-repository for all available settings. |
| 5 | + |
| 6 | + # The name of the repository. Changing this will rename the repository |
| 7 | + name: testcontainers-python |
| 8 | + |
| 9 | + # A short description of the repository that will show up on GitHub |
| 10 | + description: >- |
| 11 | + Testcontainers is a Python library that providing a friendly |
| 12 | + API to run Docker container. It is designed to create runtime environment |
| 13 | + to use during your automatic tests. |
| 14 | +
|
| 15 | + # A URL with more information about the repository |
| 16 | + homepage: https://testcontainers-python.readthedocs.io/en/latest |
| 17 | + |
| 18 | + # A comma-separated list of topics to set on the repository |
| 19 | + topics: database,python,python3,selenium,testcontainers,testing |
| 20 | + |
| 21 | + # Either `true` to make the repository private, or `false` to make it public. |
| 22 | + private: false |
| 23 | + |
| 24 | + # Either `true` to enable issues for this repository, `false` to disable them. |
| 25 | + has_issues: true |
| 26 | + |
| 27 | + # Either `true` to enable projects for this repository, or `false` to disable them. |
| 28 | + # If projects are disabled for the organization, passing `true` will cause an API error. |
| 29 | + has_projects: false |
| 30 | + |
| 31 | + # Either `true` to enable the wiki for this repository, `false` to disable it. |
| 32 | + has_wiki: false |
| 33 | + |
| 34 | + # Either `true` to enable downloads for this repository, `false` to disable them. |
| 35 | + has_downloads: true |
| 36 | + |
| 37 | + # Updates the default branch for this repository. |
| 38 | + default_branch: main |
| 39 | + |
| 40 | + # Either `true` to allow squash-merging pull requests, or `false` to prevent |
| 41 | + # squash-merging. |
| 42 | + allow_squash_merge: true |
| 43 | + |
| 44 | + # Either `true` to allow merging pull requests with a merge commit, or `false` |
| 45 | + # to prevent merging pull requests with merge commits. |
| 46 | + allow_merge_commit: false |
| 47 | + |
| 48 | + # Either `true` to allow rebase-merging pull requests, or `false` to prevent |
| 49 | + # rebase-merging. |
| 50 | + allow_rebase_merge: false |
| 51 | + |
| 52 | + # Either `true` to enable automatic deletion of branches on merge, or `false` to disable |
| 53 | + delete_branch_on_merge: true |
| 54 | + |
| 55 | +# Labels: define labels for Issues and Pull Requests |
| 56 | +# If including a `#`, make sure to wrap it with quotes! |
| 57 | +labels: |
| 58 | + - { name: '⛔ invalid', color: '#e6e6e6', description: '' } |
| 59 | + - { name: 'dependencies', color: '#0366d6', description: 'Pull requests that update a dependency file' } |
| 60 | + - { name: 'good first issue', color: '#1C49A0', description: '' } |
| 61 | + - { name: '✅ close on merge', color: '#0E8A16', description: 'Issue that will be closed by an open pull request' } |
| 62 | + - { name: '✨ package: new', color: '#0E8A16', description: '' } |
| 63 | + - { name: '❓ question', color: '#cc317c', description: '' } |
| 64 | + - { name: '🍏 macos', color: '#C5BF0',, description: '' } |
| 65 | + - { name: '🐛 bug', color: '#ee001',, description: '' } |
| 66 | + - { name: '🐧 linux', color: '#3ED4D',, description: '' } |
| 67 | + - { name: '👀 requires attention', color: '#fef2c0', description: '' } |
| 68 | + - { name: '📖 documentation', color: '#d93f0b', description: '' } |
| 69 | + - { name: '📦 package: clickhouse', color: '#0052CC', description: '' } |
| 70 | + - { name: '📦 package: compose', color: '#0052CC', description: '' } |
| 71 | + - { name: '📦 package: core', color: '#0052CC', description: '' } |
| 72 | + - { name: '📦 package: elasticsearch', color: '#0052CC', description: '' } |
| 73 | + - { name: '📦 package: google', color: '#0052CC', description: '' } |
| 74 | + - { name: '📦 package: kafka', color: '#0052CC', description: '' } |
| 75 | + - { name: '📦 package: keycloak', color: '#0052CC', description: '' } |
| 76 | + - { name: '📦 package: mongodb', color: '#0052CC', description: '' } |
| 77 | + - { name: '📦 package: mssql', color: '#0052CC', description: '' } |
| 78 | + - { name: '📦 package: neo4j', color: '#0052CC', description: '' } |
| 79 | + - { name: '📦 package: oracle', color: '#0052CC', description: '' } |
| 80 | + - { name: '📦 package: postgres', color: '#0052CC', description: '' } |
| 81 | + - { name: '📦 package: rabbitmq', color: '#0052CC', description: '' } |
| 82 | + - { name: '📦 package: selenium', color: '#0052CC', description: '' } |
| 83 | + - { name: '🔀 requires triage', color: '#bfdadc', description: '' } |
| 84 | + - { name: '🔧 maintenance', color: '#c2f759', description: '' } |
| 85 | + - { name: '🚀 enhancement', color: '#84b6eb', description: '' } |
| 86 | + - { name: '🚫 wontfix', color: '#ffffff', description: '' } |
| 87 | + - { name: '🛟 help wanted', color: '#128A0C', description: '' } |
| 88 | + |
| 89 | +# Collaborators: give specific users access to this repository. |
| 90 | +# See https://docs.github.com/en/rest/reference/repos#add-a-repository-collaborator for available options |
| 91 | +collaborators: |
| 92 | + - username: totallyzen |
| 93 | + permission: maintain |
| 94 | + - username: alexanderankin |
| 95 | + permission: maintain |
| 96 | + - username: kiview |
| 97 | + permission: admin |
| 98 | + #- username: testcontainersbot |
| 99 | + # permission: write |
| 100 | + |
| 101 | + # Note: `permission` is only valid on organization-owned repositories. |
| 102 | + # The permission to grant the collaborator. Can be one of: |
| 103 | + # * `pull` - can pull, but not push to or administer this repository. |
| 104 | + # * `push` - can pull and push, but not administer this repository. |
| 105 | + # * `admin` - can pull, push and administer this repository. |
| 106 | + # * `maintain` - Recommended for project managers who need to manage the repository without access to sensitive or destructive actions. |
| 107 | + # * `triage` - Recommended for contributors who need to proactively manage issues and pull requests without write access. |
| 108 | + |
| 109 | +# See https://docs.github.com/en/rest/reference/teams#add-or-update-team-repository-permissions for available options |
| 110 | +teams: |
| 111 | + # Please make sure the team already exist in the organization, as the repository-settings application is not creating them. |
| 112 | + # See https://github.com/repository-settings/app/discussions/639 for more information about teams and settings |
| 113 | + # - name: go-team |
| 114 | + # # The permission to grant the team. Can be one of: |
| 115 | + # # * `pull` - can pull, but not push to or administer this repository. |
| 116 | + # # * `push` - can pull and push, but not administer this repository. |
| 117 | + # # * `admin` - can pull, push and administer this repository. |
| 118 | + # # * `maintain` - Recommended for project managers who need to manage the repository without access to sensitive or destructive actions. |
| 119 | + # # * `triage` - Recommended for contributors who need to proactively manage issues and pull requests without write access. |
| 120 | + # permission: admin |
| 121 | + - name: oss-maintainers |
| 122 | + permission: admin |
| 123 | + |
| 124 | +branches: |
| 125 | + - name: main |
| 126 | + # https://docs.github.com/en/rest/reference/repos#update-branch-protection |
| 127 | + # Branch Protection settings. Set to null to disable |
| 128 | + protection: |
| 129 | + # Required. Require at least one approving review on a pull request, before merging. Set to null to disable. |
| 130 | + required_pull_request_reviews: |
| 131 | + # The number of approvals required. (1-6) |
| 132 | + required_approving_review_count: 1 |
| 133 | + # Dismiss approved reviews automatically when a new commit is pushed. |
| 134 | + dismiss_stale_reviews: false |
| 135 | + # Blocks merge until code owners have reviewed. |
| 136 | + require_code_owner_reviews: false |
| 137 | + # Specify which users and teams can dismiss pull request reviews. Pass an empty dismissal_restrictions object to disable. User and team dismissal_restrictions are only available for organization-owned repositories. Omit this parameter for personal repositories. |
| 138 | + dismissal_restrictions: |
| 139 | + users: [] |
| 140 | + teams: [] # [go-team] |
| 141 | + # Required. Require status checks to pass before merging. Set to null to disable |
| 142 | + required_status_checks: |
| 143 | + # Required. Require branches to be up to date before merging. |
| 144 | + strict: false |
| 145 | + # Required. The list of status checks to require in order to merge into this branch |
| 146 | + contexts: [] |
| 147 | + # - "core / test (ubuntu, 3.11)" |
| 148 | + # Required. Enforce all configured restrictions for administrators. Set to true to enforce required status checks for repository administrators. Set to null to disable. |
| 149 | + enforce_admins: false |
| 150 | + # Prevent merge commits from being pushed to matching branches |
| 151 | + required_linear_history: true |
| 152 | + # Required. Restrict who can push to this branch. Team and user restrictions are only available for organization-owned repositories. Set to null to disable. |
| 153 | + restrictions: |
| 154 | + apps: [] |
| 155 | + users: [kiview,totallyzen,alexanderankin] |
| 156 | + teams: [oss-maintainers] |
0 commit comments