This is an automated email from the ASF dual-hosted git repository.
djwang pushed a commit to branch main
in repository https://gitbox.apache.org/repos/asf/cloudberry-devops-release.git
The following commit(s) were added to refs/heads/main by this push:
new 72e5f06 Add asf-yaml and basic community files
72e5f06 is described below
commit 72e5f06a7cdf6e807b255717ffe5681a122da474
Author: Dianjin Wang <[email protected]>
AuthorDate: Tue Nov 5 14:21:11 2024 +0800
Add asf-yaml and basic community files
---
.asf.yaml | 73 +++++++++++++++++++++++++++++++++++++++++++++++++++++++++
CONTRIBUTING.md | 66 +++++++++++++++++++++++++++++++++++++++++++++++++++
README.md | 1 +
3 files changed, 140 insertions(+)
diff --git a/.asf.yaml b/.asf.yaml
new file mode 100644
index 0000000..ee80d82
--- /dev/null
+++ b/.asf.yaml
@@ -0,0 +1,73 @@
+#
+# Licensed to the Apache Software Foundation (ASF) under one or more
+# contributor license agreements. See the NOTICE file distributed with
+# this work for additional information regarding copyright ownership.
+# The ASF licenses this file to You under the Apache License, Version 2.0
+# (the "License"); you may not use this file except in compliance with
+# the License. You may obtain a copy of the License at
+#
+# http://www.apache.org/licenses/LICENSE-2.0
+#
+# Unless required by applicable law or agreed to in writing, software
+# distributed under the License is distributed on an "AS IS" BASIS,
+# WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+# See the License for the specific language governing permissions and
+# limitations under the License.
+#
+
+github:
+ description: DevOps and Release for Apache Cloudberry (Incubating)
+ homepage: https://cloudberry.apache.org
+ labels:
+ - mpp
+ - big-data
+ - data-warehouse
+ - data-analysis
+ - olap
+ - distributed-database
+ - database
+ - postgres
+ - postgresql
+ - greenplum
+ - cloudberry
+ - ai
+ - devops
+ features:
+ # Enable wiki for documentation
+ wiki: false
+ # Enable issues management
+ issues: true
+ # Enable projects for project management boards
+ projects: false
+ enabled_merge_buttons:
+ # enable squash button:
+ squash: true
+ # disable merge button:
+ merge: false
+ # enable rebase button:
+ rebase: true
+ protected_branches:
+ main:
+ required_status_checks:
+ # strict means "Require branches to be up to date before merging".
+ strict: true
+ required_pull_request_reviews:
+ dismiss_stale_reviews: true
+ required_approving_review_count: 1
+ # squash or rebase must be allowed in the repo for this setting to be
set to true.
+ required_linear_history: true
+
+ required_signatures: false
+
+ # requires all conversations to be resolved before merging is possible
+ required_conversation_resolution: true
+ del_branch_on_merge: true
+ dependabot_alerts: true
+ dependabot_updates: false
+ protected_tags:
+ - "[0-9]*.*"
+notifications:
+ commits: [email protected]
+ issues: [email protected]
+ pullrequests: [email protected]
+ pullrequests_bot_dependabot: [email protected]
diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md
new file mode 100644
index 0000000..b00691f
--- /dev/null
+++ b/CONTRIBUTING.md
@@ -0,0 +1,66 @@
+Apache Cloudberry welcomes contributions from anyone, new and
+experienced! We appreciate your interest in contributing. This guide
+will help you get started with the contribution.
+
+## Code of Conduct
+
+Everyone who participates in Cloudberry, either as a user or a
+contributor, is obliged to follow the ASF Code of Conduct.
+
+## GitHub Contribution Workflow
+
+1. Fork this repo to your own GitHub account.
+2. Clone down the repo to your local system.
+
+```
+git clone https://github.com/your-user-name/cloudberry-devops-release.git
+```
+
+3. Add the upstream repo. (You only have to do this once, not every time.)
+
+```
+git remote add upstream https://github.com/apache/cloudberry-devops-release.git
+```
+
+4. Create a new branch to hold your work.
+
+```
+git checkout -b new-branch-name
+```
+
+5. Work on your new code.
+
+6. Commit your changes.
+
+```
+git add <the change files>
+git commit
+```
+
+7. Push your changes to your GitHub repo.
+
+```
+git push origin new-branch-name
+```
+
+8. Open a PR(Pull Request).
+
+Go to the repo on GitHub. There will be a message about your recently pushed
+branch, asking if you would like to open a pull request. Follow the prompts,
+compare across repositories, and submit the PR.
+
+9. Get your code reviewed.
+
+10. Congratulations! Once your PR is approved, then the code will be
+merged. Your code will be shipped in the recent future releases.
+
+## Sync your branch with the upstream
+
+Before working on your next contribution, make sure your local repository is
+up to date:
+
+```
+git checkout main
+git fetch upstream
+git rebase upstream/main
+```
diff --git a/README.md b/README.md
new file mode 100644
index 0000000..9602438
--- /dev/null
+++ b/README.md
@@ -0,0 +1 @@
+# DevOps and Release for Apache Cloudberry (Incubating)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
