Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

MeGit writes to ~/.eclipse and this conflicts with Eclipse

Open
#69 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
25/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Stale
Tech stack
git, java
Domain
desktop

Research direction

Start by tracing how MeGit handles the selected workspace and writes to ~/.eclipse, then compare that behavior with Eclipse's configuration handling. Done means MeGit no longer conflicts with Eclipse's plugins or configuration, including the reported CoPilot prompt.

Written by the indexing model from the issue text.

Description

As per the title, I can see that Megit write stuff onto ~/.eclipse (in macOS 26.2), despite I selected a different workspace directory in the splash screen.

Already annoying in Eclipse, when it happens with MeGit, conflicts pop up. In fact, MeGit has just asked me if I want to reinstall plugins like CoPilot, which I've never installed in MeGit, but I've installed it in Eclipse.

I know this is a long-standing Eclipse problem, but it would be great if MeGit could do something for itself.

Dominant language
Java
Stars
558
Forks
57
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

  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 eclipsesource/megit

All issues in eclipsesource/megit

Similar issues

More Java issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.