woodpecker-ci / woodpecker-ci/plugin-git
Use local git config
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 25
- Forks
- 40
- Avg merge
- 22h 23m
- Merged PRs (30d)
- 6
Description
the global git config change:
git config --global --replace-all safe.directory *
only works if we have exclusive access to the home directory.
In some edgecases with local backend, this is not the case.
As for example if you need to use to use a pre defined user environment for certain tools that where pre-configured,
you have to use the no isolated home option: https://github.com/woodpecker-ci/woodpecker/pull/6251
You get
To make this plugin more portable, we need to look into let git-config read from workflow based path.
Contributor 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.
Research direction
Start by locating where the plugin runs git config --global --replace-all safe.directory * and review how workflow paths are exposed to the plugin. Determine how Git can read configuration from a workflow-based path, then verify the clone setup also works with the no-isolated-home option without requiring exclusive access to the home directory.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- git, go
- Domain
- ci-cd
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100