Correct graphouse version when making new Branches or Changes
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 35/100
- Issue type
- Bug
- Clarity
- Needs clarification
- Activity status
- Stale
- Tech stack
- java
- Domain
- build-system
Research direction
Start with build.gradle at line 18, as linked in the issue, and inspect how the Graphouse version is declared. Compare that value with the actual git branch or tag; done means new branches or changes report the corresponding version and are not marked as snapshots.
Written by the indexing model from the issue text.
Description
I think should be corrected and reflect the actual git branch/tag version... Also this is no should be considered snapshot as we a using it... 😄
https://github.com/yandex/graphouse/blob/d368c1150700adce07e5232d4b68eff28c1e3ffb/build.gradle#L18
- Dominant language
- Java
- Stars
- 260
- Forks
- 55
- PR merge metrics
- No merged PRs in 30d
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from ClickHouse/graphouse
-
Difficulty 5/5 Over a week Newbie friendliness 20/100
ClickHouse/graphouse#150 ·
-
Difficulty 4/5 3-5 days Newbie friendliness 35/100
ClickHouse/graphouse#140 · 1 comment ·
-
support for pickleOpen
Difficulty 5/5 Over a week Newbie friendliness 30/100
ClickHouse/graphouse#114 ·
-
Difficulty 3/5 1-2 days Newbie friendliness 45/100
ClickHouse/graphouse#98 ·
-
Difficulty 3/5 1-2 days Newbie friendliness 35/100
ClickHouse/graphouse#77 · 3 comments ·
All issues in ClickHouse/graphouse
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
Maintainers usually reply within 3 days
-
A proxy that fails to start logs a RejectedExecutionException stack trace from its shutdown hookOpenfollow-up
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
Sanne/incus-spawn#1953 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
atlassian/data-center-helm-charts#1170 ·
Maintainers usually reply within 1 day
-
Bug
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
Maintainers usually reply within 1 day
-
Issue: Bug
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
OpenAPITools/openapi-generator#25524 ·
Maintainers usually reply within 1 day