Gemfile.lock Handling verbessern

Open
#83 0 comments 0 reactions 0 assignees View on GitHub

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

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

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from hitobito/development

All issues in hitobito/development

Similar issues

More Shell/Bash issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.