Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Deleted files are not committed to the remote repo

See original GitHub issue

I have a library build baked by rollup with multiple entry points. Rollup finds common dependencies and hashes them, so that after each release I end up with dirty files, being deleted but not commited:

On branch master
Your branch is ahead of 'origin/master' by 1 commit.
  (use "git push" to publish your local commits)

Changes not staged for commit:
  (use "git add/rm <file>..." to update what will be committed)
  (use "git checkout -- <file>..." to discard changes in working directory)

	deleted:    dist/confiig-93410e72.js
	deleted:    dist/definition-3fd983cb.js

New files are dist/config-8a65f714.js and dist/definition-4e23ca7b.js.

Edit:

.releaserc:

{
  "plugins": [
    "@semantic-release/commit-analyzer",
    "@semantic-release/release-notes-generator",
    ["@semantic-release/changelog", {
      "changelogFile": "CHANGELOG.md"
    }],
    ["@semantic-release/npm", {
      "npmPublish": true,
    }],
    ["@semantic-release/git", {
      "assets": ["dist/**/*.{js,css}", "CHANGELOG.md", "package.json"],
      "message": "chore(release): ${nextRelease.version} [skip ci]\n\n${nextRelease.notes}"
    }]
  ],
  "branch": "master",
  "dryRun": false,
  "ci": false,
}

`package.json`: (only related)

```json
{
  "devdependencies": {
    "@semantic-release/changelog": "^3.0.4",
    "@semantic-release/git": "^7.0.16",
    "semantic-release": "^15.13.24"  
  }
}