Suggested workflow for putting reusable code in packages.

Hello. We are looking into trying to extract our reusable code into packages for future reuse.
We have managed to set up a git repo with a package (PackageA) that can be loaded into a projects as a dependency in the manifest file.

How ever, we want to split our code up into several packages. Not just one giant one.
To do this, we need PackageB to be able to depend on PackageA.

package.json (PackageB)

{
"com.sareptastudio.framework" : "1.0.0"
}```
**manifest.json (PackageB project)**
```"dependencies":
{
...
"com.sareptastudio.framework": "git://repopath..."
}```
We have a unity project dedicated to developing this package. Where the Assets folder is set up as a git repo to be able to push directly to the package repo, and have everything in the root.
But we get some errors trying to import our dependency PackageA.

GUID [f57eeac6cfea5e14794e727e141fed05] for asset 'Packages/com.sareptastudio.framework/CHANGELOG.md' conflicts with:
'Assets/CHANGELOG.md' (current owner)
We can't assign a new GUID because the asset is in an immutable folder. The asset will be ignored.

This warning (error really!) occurs for all standardized folders as well. Preventing them from being imported.
Ex. Editor, Runtime, Tests, etc...

Are we doing something wrong here? How do we prevent this duplicate GUID issues?
I saw a suggestion to manually regenerate them on a webpage and replace them. But this is not a feasible option!

I have found a potential workaround.

If you import the package while not having any content in PackageB it will import correctly.
From there you can proceed to create new folders and files without issues.

How ever, I have a feeling this is just concealing the problem and not actually fixing it.
If you were to import a new version of PackageA in the future. Would it not cause this problem again?

I’d post this question in the package manager forums.

Thanks, I was not aware there was one.
I also think I found that what is causing this is an under-laying problem where the package doesn’t actually load correctly!