Gemfile.lock Handling verbessern
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 35/100
- Issue type
- Feature
- Clarity
- Mostly clear
- Activity status
- Stale
- Tech stack
- ruby
- Domain
- developer-experience
Research direction
Start by inspecting the development setup flow and how Gemfile.lock is currently copied from Core. Compare the proposed GitHub Action synchronization with the Gemfile.local and Gemfile.lock.local approach from native-ruby-Setup. Done means setup no longer requires manually copying Gemfile.lock and the chosen approach is documented or tested.
Written by the indexing model from the issue text.
Description
Aktuell muss während dem Setup das Gemfile.lock einmalig manuell aus dem Core kopiert werden.
Dies könnte auch automatisiert werden. Z.B. via GitHub Action, welche das Gemfile.lock ins Development Repo synct, oder indem der Trick mit Gemfile.local und Gemfile.lock.local vom native-ruby-Setup verwendet wird.
- Dominant language
- Shell
- Stars
- 23
- Forks
- 18
- Avg merge
- 1h 28m
- Merged PRs (30d)
- 1
Getting set up
- Ships a Dockerfile or Docker Compose file
- No pull request template
- No contributing guide
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 hitobito/development
-
bug
Difficulty 3/5 1-2 days Newbie friendliness 30/100
hitobito/development#74 · 1 comment ·
-
bug
Difficulty 3/5 1-2 days Newbie friendliness 48/100
hitobito/development#72 · 2 reactions ·
-
Difficulty 4/5 3-5 days Newbie friendliness 30/100
hitobito/development#48 · 1 comment ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 25/100
hitobito/development#23 ·
-
Difficulty 3/5 1-2 days Newbie friendliness 45/100
hitobito/development#15 ·
All issues in hitobito/development
Similar issues
-
bot-found documentation priority: P3
Difficulty 1/5 1-3 hours Newbie friendliness 88/100
madenvel/KalinkaPlayer#602 ·
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
huggingface/kernels#1006 ·
Maintainers usually reply within 1 day
-
Difficulty 1/5 Under an hour Newbie friendliness 94/100
Maintainers usually reply within 2 days
-
severity: low
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
luainkernel/lunatik#2594 ·
Maintainers usually reply within 1 day