Why ".gitignore" is ignored ?

Open
#345 6 comments 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, javascript
Domain
release

Research direction

Read lib/git.js around line 19 and the linked commit to understand why ignored files are added to the next commit. Trace the release-asset flow and any related tests, then seek a maintainer decision on whether this behavior should change; the issue provides no acceptance criteria for a completed change.

Written by the indexing model from the issue text.

Description

Hi!
I'd like to understand the motivation for adding files that are ignored to the next commit.

For example, my project build outputs code into a dist folder. This should be published as part of the artifact on the registry.
But I don't want to find those dist files in the code (pollution IMO).

It seems like a common use case. Am I the only one troubled by this?

Thanks,

Dominant language
JavaScript
Stars
339
Forks
75
Avg merge
5h 15m
Merged PRs (30d)
6

Contributor guide

No contributing guide indexed for this repository

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 semantic-release/git

All issues in semantic-release/git

Similar issues

More JavaScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.