Skip to content

Commit

Permalink
Merge pull request #656 from Altinity/tmp/fix_issues_of_antalya_as_de…
Browse files Browse the repository at this point in the history
…fault_branch

Antalya: fix issues of `antalya` as default branch
  • Loading branch information
Enmk authored Feb 25, 2025
2 parents e115fd1 + 8d98e17 commit 0af9297
Show file tree
Hide file tree
Showing 20 changed files with 912 additions and 1,057 deletions.
16 changes: 16 additions & 0 deletions .github/ISSUE_TEMPLATE/10_question.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,16 @@
---
name: Question
about: Ask a question about an Altinity Stable Build
title: ''
labels: question
assignees: ''

---

Make sure to check the [Altinity documentation](https://docs.altinity.com/) and the [Altinity Knowledge Base](https://kb.altinity.com/) first.

If your question is concise and probably has a short answer, asking it in the [the Altinity Slack channel](https://altinitydbworkspace.slack.com/join/shared_invite/zt-1togw9b4g-N0ZOXQyEyPCBh_7IEHUjdw#/shared-invite/email) is probably the fastest way to find the answer.

For more complicated questions, consider [asking them on StackOverflow with the tag "clickhouse"](https://stackoverflow.com/questions/tagged/clickhouse).

If you'd rather file a GitHub issue, remove all this text and ask your question here.
20 changes: 0 additions & 20 deletions .github/ISSUE_TEMPLATE/10_question.yaml

This file was deleted.

50 changes: 50 additions & 0 deletions .github/ISSUE_TEMPLATE/15_bug-report.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,50 @@
---
name: Bug report
about: Report something broken in an Altinity Stable Build
title: ''
labels: 'potential bug'
assignees: ''

---

*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.*

## Type of problem
Choose one of the following items, then delete the others:

**Bug report** - something's broken

**Incomplete implementation** - something's not quite right

**Performance issue** - something works, just not as quickly as it should

**Backwards compatibility issue** - something used to work, but now it doesn't

**Unexpected behavior** - something surprising happened, but it wasn't the good kind of surprise

**Installation issue** - something doesn't install the way it should

**Usability issue** - something works, but it could be a lot easier

**Documentation issue** - something in the docs is wrong, incomplete, or confusing

## Describe the situation
A clear, concise description of what's happening. Can you reproduce it in a ClickHouse Official build of the same version?

## How to reproduce the behavior

* Which Altinity Stable Build version to use
* Which interface to use, if it matters
* Non-default settings, if any
* `CREATE TABLE` statements for all tables involved
* Sample data for all these tables, use the [clickhouse-obfuscator](https://github.com/ClickHouse/ClickHouse/blob/31fd4f5eb41d5ec26724fc645c11fe4d62eae07f/programs/obfuscator/README.md) if necessary
* Queries to run that lead to an unexpected result

## Expected behavior
A clear, concise description of what you expected to happen.

## Logs, error messages, stacktraces, screenshots...
Add any details that might explain the issue.

## Additional context
Add any other context about the issue here.
28 changes: 9 additions & 19 deletions .github/ISSUE_TEMPLATE/20_feature-request.md
Original file line number Diff line number Diff line change
@@ -1,30 +1,20 @@
---
name: Feature request
about: Suggest an idea for ClickHouse
about: Suggest a new ClickHouse feature
title: ''
labels: feature
assignees: ''

---

> (you don't have to strictly follow this form)
## Describe the new feature
A clear, concise description of the feature you'd like to see.

**Company or project name**
## Use case
What is a situation where this feature would be useful? How common is that situation?

> Put your company name or project description here
## Alternative solutions
Are there other ways to solve the problem this new feature addresses? Are any of them possible now? If so, how would the solution you're proposing be better?

**Use case**

> A clear and concise description of what the intended usage scenario is.
**Describe the solution you'd like**

> A clear and concise description of what you want to happen.
**Describe alternatives you've considered**

> A clear and concise description of any alternative solutions or features you've considered.
**Additional context**

> Add any other context or screenshots about the feature request here.
## Additional context
Add any other context about your proposed feature here.
34 changes: 0 additions & 34 deletions .github/ISSUE_TEMPLATE/30_unexpected-behaviour.md

This file was deleted.

34 changes: 0 additions & 34 deletions .github/ISSUE_TEMPLATE/35_incomplete_implementation.md

This file was deleted.

33 changes: 0 additions & 33 deletions .github/ISSUE_TEMPLATE/45_usability-issue.md

This file was deleted.

26 changes: 0 additions & 26 deletions .github/ISSUE_TEMPLATE/50_build-issue.md

This file was deleted.

18 changes: 0 additions & 18 deletions .github/ISSUE_TEMPLATE/60_documentation-issue.md

This file was deleted.

30 changes: 0 additions & 30 deletions .github/ISSUE_TEMPLATE/70_performance-issue.md

This file was deleted.

30 changes: 0 additions & 30 deletions .github/ISSUE_TEMPLATE/80_backward-compatibility.md

This file was deleted.

57 changes: 0 additions & 57 deletions .github/ISSUE_TEMPLATE/85_bug-report.md

This file was deleted.

Loading

0 comments on commit 0af9297

Please sign in to comment.