Skip to content

Commit 86d4e0d

Browse files
authored
Merge pull request #1116 from Altinity/rebase-cicd-v25.3.8.23-lts
Rebase CICD on v25.3.8.23-lts
2 parents 4149650 + 8200cc3 commit 86d4e0d

File tree

226 files changed

+6391
-8452
lines changed

Some content is hidden

Large Commits have some content hidden by default. Use the searchbox below for content that may be hidden.

226 files changed

+6391
-8452
lines changed
Lines changed: 36 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,36 @@
1+
---
2+
name: Project Antalya Bug Report
3+
about: Help us improve Project Antalya
4+
title: ''
5+
labels: antalya
6+
assignees: ''
7+
8+
---
9+
10+
**Describe the bug**
11+
A clear and concise description of what the bug is.
12+
13+
14+
**To Reproduce**
15+
Steps to reproduce the behavior:
16+
1. Go to '...'
17+
2. Click on '....'
18+
3. Scroll down to '....'
19+
4. See error
20+
21+
**Expected behavior**
22+
A clear and concise description of what you expected to happen.
23+
24+
**Screenshots**
25+
If applicable, add screenshots to help explain your problem.
26+
27+
**Key information**
28+
Provide relevant runtime details.
29+
- Project Antalya Build Version
30+
- Cloud provider, e.g., AWS
31+
- Kubernetes provider, e.g., GKE or Minikube
32+
- Object storage, e.g., AWS S3 or Minio
33+
- Iceberg catalog, e.g., Glue with REST Proxy
34+
35+
**Additional context**
36+
Add any other context about the problem here.

.github/ISSUE_TEMPLATE/10_question.yaml

Lines changed: 0 additions & 20 deletions
This file was deleted.

.github/ISSUE_TEMPLATE/20_feature-request.yaml

Lines changed: 0 additions & 38 deletions
This file was deleted.
Lines changed: 20 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,20 @@
1+
---
2+
name: Project Antalya Feature request
3+
about: Suggest an idea for Project Antalya
4+
title: ''
5+
labels: antalya, enhancement
6+
assignees: ''
7+
8+
---
9+
10+
**Is your feature request related to a problem? Please describe.**
11+
A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]
12+
13+
**Describe the solution you'd like**
14+
A clear and concise description of what you want to happen.
15+
16+
**Describe alternatives you've considered**
17+
A clear and concise description of any alternative solutions or features you've considered.
18+
19+
**Additional context**
20+
Add any other context or screenshots about the feature request here.
Lines changed: 16 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,16 @@
1+
---
2+
name: Project Antalya Question
3+
about: Ask a question about Project Antalya
4+
title: ''
5+
labels: ''
6+
assignees: ''
7+
8+
---
9+
10+
Make sure to check the [Altinity documentation](https://docs.altinity.com/) and the [Altinity Knowledge Base](https://kb.altinity.com/) first.
11+
12+
If your question is concise and probably has a short answer, asking it in the [the Altinity Slack workspace](https://altinity.com/slack) is probably the fastest way to find the answer. Use the #antalya channel.
13+
14+
If you'd rather file a GitHub issue, remove all this text and ask your question here.
15+
16+
Please include relevant environment information as applicable.

.github/ISSUE_TEMPLATE/30_unexpected-behaviour.yaml

Lines changed: 0 additions & 50 deletions
This file was deleted.

.github/ISSUE_TEMPLATE/35_incomplete_implementation.yaml

Lines changed: 0 additions & 50 deletions
This file was deleted.
Lines changed: 50 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,50 @@
1+
---
2+
name: Altinity Stable Bug report
3+
about: Report something broken in an Altinity Stable Build
4+
title: ''
5+
labels: stable
6+
assignees: ''
7+
8+
---
9+
10+
*I checked [the Altinity Stable Builds lifecycle table](https://docs.altinity.com/altinitystablebuilds/#altinity-stable-builds-life-cycle-table), and the Altinity Stable Build version I'm using is still supported.*
11+
12+
## Type of problem
13+
Choose one of the following items, then delete the others:
14+
15+
**Bug report** - something's broken
16+
17+
**Incomplete implementation** - something's not quite right
18+
19+
**Performance issue** - something works, just not as quickly as it should
20+
21+
**Backwards compatibility issue** - something used to work, but now it doesn't
22+
23+
**Unexpected behavior** - something surprising happened, but it wasn't the good kind of surprise
24+
25+
**Installation issue** - something doesn't install the way it should
26+
27+
**Usability issue** - something works, but it could be a lot easier
28+
29+
**Documentation issue** - something in the docs is wrong, incomplete, or confusing
30+
31+
## Describe the situation
32+
A clear, concise description of what's happening. Can you reproduce it in a ClickHouse Official build of the same version?
33+
34+
## How to reproduce the behavior
35+
36+
* Which Altinity Stable Build version to use
37+
* Which interface to use, if it matters
38+
* Non-default settings, if any
39+
* `CREATE TABLE` statements for all tables involved
40+
* Sample data for all these tables, use the [clickhouse-obfuscator](https://github.com/ClickHouse/ClickHouse/blob/31fd4f5eb41d5ec26724fc645c11fe4d62eae07f/programs/obfuscator/README.md) if necessary
41+
* Queries to run that lead to an unexpected result
42+
43+
## Expected behavior
44+
A clear, concise description of what you expected to happen.
45+
46+
## Logs, error messages, stacktraces, screenshots...
47+
Add any details that might explain the issue.
48+
49+
## Additional context
50+
Add any other context about the issue here.

.github/ISSUE_TEMPLATE/45_usability-issue.yaml

Lines changed: 0 additions & 50 deletions
This file was deleted.
Lines changed: 16 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,16 @@
1+
---
2+
name: Altinity Stable Question
3+
about: Ask a question about an Altinity Stable Build
4+
title: ''
5+
labels: question, stable
6+
assignees: ''
7+
8+
---
9+
10+
Make sure to check the [Altinity documentation](https://docs.altinity.com/) and the [Altinity Knowledge Base](https://kb.altinity.com/) first.
11+
12+
If your question is concise and probably has a short answer, asking it in the [the Altinity Slack channel](https://altinity.com/slack) is probably the fastest way to find the answer.
13+
14+
For more complicated questions, consider [asking them on StackOverflow with the tag "clickhouse"](https://stackoverflow.com/questions/tagged/clickhouse).
15+
16+
If you'd rather file a GitHub issue, remove all this text and ask your question here.

0 commit comments

Comments
 (0)